Improve OAuth handling in headless environments#15
Improve OAuth handling in headless environments#15google-labs-jules[bot] wants to merge 1 commit into
Conversation
- Explicitly check for cached token validity when SPOTIPY_REDIRECT_URI is missing. - Warn user via stderr if no valid token is found and redirect URI is missing, explaining the default behavior (localhost). - Add unit tests for CLI OAuth warning logic.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
This change improves the robustness of the
track --likedcommand when running in a headless environment withoutSPOTIPY_REDIRECT_URIset. Previously, it would silently attempt OAuth flow which defaults to localhost, potentially confusing users or hanging if they expected automatic browser opening. Now, it validates the cached token first and prints a clear warning if manual intervention is likely required.PR created automatically by Jules for task 11460776107575371971 started by @opbenesh