apunkt/rowboat
1
0
Fork 0
mirror of https://github.com/rowboatlabs/rowboat.git synced 2026-05-10 15:52:38 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

fix: stop Gmail sync from throwing "No refresh token is set" in rowboat mode

Browse source 
In rowboat OAuth mode the OAuth2Client is built without a refresh_token
because refreshes go through the api. google-auth-library's default
5-minute eagerRefreshThresholdMillis caused it to attempt a refresh
whenever a Gmail call landed within 5 minutes of token expiry, throwing
"No refresh token is set." before our proactive 60s-margin refresh
could run. Disabling the eager window lets our getClient() refresh path
own all refreshes as the comment intends.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Ramnique Singh 2026-05-08 13:16:46 +05:30
parent f5bba5e271
commit acff502f42
1 changed files with 7 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

7
apps/x/packages/core/src/knowledge/google-client-factory.ts
View file

@ -293,9 +293,16 @@ export class GoogleClientFactory {
* Rowboat OAuth2Client — no client_id/secret, no refresh_token.
* Library auto-refresh is disabled by absence of refresh_token; our
* proactive refresh in getClient() is the only refresh path.
*
* eagerRefreshThresholdMillis must be 0: the library defaults to a
* 5-minute window where it preemptively refreshes any token nearing
* expiry. Without a refresh_token on the client, that path throws
* "No refresh token is set." and the API call fails — even though
* our proactive refresh would have handled it on the next tick.
*/
private static createRowboatClient(tokens: OAuthTokens): OAuth2Client {
const client = new OAuth2Client();
client.eagerRefreshThresholdMillis = 0;
client.setCredentials({
access_token: tokens.access_token,
expiry_date: tokens.expires_at * 1000,