Skip to content

fix(gmail): preserve --client context in watch serve push handling#411

Open
chrysb wants to merge 1 commit intosteipete:mainfrom
chrysb:fix/gmail-watch-serve-client-context
Open

fix(gmail): preserve --client context in watch serve push handling#411
chrysb wants to merge 1 commit intosteipete:mainfrom
chrysb:fix/gmail-watch-serve-client-context

Conversation

@chrysb
Copy link

@chrysb chrysb commented Mar 4, 2026

Summary

  • preserve the selected --client override for request-time contexts inside gmail watch serve
  • wrap newService in GmailWatchServeCmd.Run so push handler API calls do not fall back to client default
  • add regression coverage in TestGmailWatchServeCmd_PreservesClientOverrideForRequestContexts

Fixes #410.

Test plan

  • docker run --rm -v \"$PWD:/src\" -w /src golang:1.25 go test ./internal/cmd -run \"TestGmailWatchServeCmd_PreservesClientOverrideForRequestContexts\"
  • Manual validation in a Docker container environment using patched gog: gog --client personal gmail watch serve ...
  • Confirm push handling no longer logs auth required ... (client default) for non-default client path under patched binary

Ensure gmail watch serve re-applies the selected OAuth client to request-time contexts before creating Gmail services, so push handling does not fall back to client default in multi-client setups.
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.

gmail watch serve ignores --client flag for push handler API calls

1 participant