Validate api_url scheme; fail early with clear errors #178
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
kallakuripraphul
changed the title
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.
why
Following the quickstart, calling
await stagehand.init()can fail with:UnsupportedProtocol: Request URL is missing an 'http://' or 'https://' protocol.
This happens when
api_urlis unset or set without a scheme (e.g.,"api.stagehand.browserbase.com/v1").what changed
api_urlinStagehand.__init__http://orhttps://→ raise:Relation to fix bug on api_url load from .env #116
Related: #116 . This PR is similar to #116 by catching misconfigurations (missing scheme / empty) before reaching httpx,