Skip to content

additional scale / browser window cleanup to properly support QA: #2663

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

Merged
merged 10 commits into from
Jun 12, 2025

Conversation

ikreymer
Copy link
Member

  • follow up to Allow users to run crawls with 1 or 2 browser windows #2627
  • use qa_num_browser_windows to set exact number of QA browsers, fallback to qa_scale
  • set num_browser_windows and num_browsers_per_pod using crawler / qa values depending if QA crawl
  • scale_from_browser_windows() accepts optional browsers_per_pod if dealing with possible QA override
  • store 'desiredScale' in CrawlStatus to avoid recomputing for later scale resolving
  • ensure status.scale is always the actual scale observed

- use qa_num_browser_windows to set exact number of QA browsers, fallback to qa_scale
- set num_browser_windows and num_browsers_per_pod using crawler / qa values depending if QA crawl
- scale_from_browser_windows() accepts optional browsers_per_pod if dealing with possible QA override
- store 'desiredScale' in CrawlStatus to avoid recomputing for later scale resolving
- ensure status.scale is always the actual scale observed
@ikreymer ikreymer requested a review from tw4l June 11, 2025 05:10
Copy link
Member

@tw4l tw4l left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested on dev, looking good! Nice to see a bit of simplification/consistency added here.

@tw4l tw4l merged commit d4a2a66 into main Jun 12, 2025
25 checks passed
@tw4l tw4l deleted the scale-fix-for-qa branch June 12, 2025 17:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants