Fix gh auth status false negative detection in LinearSolveAutotune #704
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.
Summary
Fixes false negative authentication detection when
gh auth login
appears to fail but authentication actually succeeds.Problem
As reported, when using
gh auth login
in LinearSolveAutotune:gh auth login
returns non-zero exit code due to browser failureRoot Cause
gh auth status
outputs to stderr, not stdoutgh auth login
failed (even if auth succeeded), the code gave upSolution
1. Properly Capture stderr
2. Always Check Auth Status
gh auth login
returns non-zero exit, still check auth status3. Improved Feedback
Testing
Tested scenarios:
Example
Before fix:
After fix:
This ensures authentication is properly detected even when the browser opening fails.
🤖 Generated with Claude Code
Co-Authored-By: Claude [email protected]