Hi there! Coming from node-fetch for the h2 support. Everything looked great when I first made the swap, but I just noticed that if I leave the app open for a while, subsequent requests will all end up getting this error:
err: {
"type": "RetryError",
"message": "ERR_HTTP2_GOAWAY_SESSION",
"stack":
Error: ERR_HTTP2_GOAWAY_SESSION
at doFetch (C:\Users\Lewis\Develop\reflame\code\agent\node_modules\fetch-h2\dist\lib\fetch-http2.js:56:23)
}
The only way to recover I've found was to restart the app, which is obviously not great. 😅
I followed the error trace to this line:
|
if ( err.code === "ERR_HTTP2_GOAWAY_SESSION" ) |
The comment above says // Retry with new session, but the code itself just throws. Maybe the retry behavior hasn't been implemented yet?
Hi there! Coming from node-fetch for the h2 support. Everything looked great when I first made the swap, but I just noticed that if I leave the app open for a while, subsequent requests will all end up getting this error:
The only way to recover I've found was to restart the app, which is obviously not great. 😅
I followed the error trace to this line:
fetch-h2/lib/fetch-http2.ts
Line 137 in 502c7da
The comment above says
// Retry with new session, but the code itself just throws. Maybe the retry behavior hasn't been implemented yet?