DRU-619 -- Use supported browser session launch arguments - #673
Merged
Merged
Conversation
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
1 participant
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.
A workflow that opens a saved browser session exits with
usage: session-launch --headed|--headless.BrowserSession._launchpasses--drive, but the shipped launcher rejects every extra argument. Daily Quote reproduced this in production after its login was saved successfully.Pass only the selected headed/headless mode, matching the launcher and the existing login-window command. Remove the stale command comment and correct the two existing command assertions. No new tests or browser-image changes.
Validation: Ruff lint and format checks passed;
git diff --checkpassed. Tests were not run, as requested. The fixed command has not been deployed or exercised against a live browser.Tracks DRU-619.