DF-26076: Fix GSR adapter hourly WebSocket disconnections - #5252
DF-26076: Fix GSR adapter hourly WebSocket disconnections#5252cl-efornaciari wants to merge 16 commits into
Conversation
🦋 Changeset detectedLatest commit: e45050c The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
…tions (DF-26076) GSR API issues 1-hour validity tokens and closes connections when they expire. The adapter now caches tokens and proactively refreshes them 5 minutes before expiry to prevent ungraceful server-side disconnections. - Extract token expiry time from GSR auth response - Implement token caching with automatic refresh - Schedule proactive reconnection before token expiry - Add comprehensive unit and integration tests Fixes DF-26076
…tions (DF-26076) GSR API issues 1-hour validity tokens and closes connections when they expire. The adapter now caches tokens and proactively refreshes them 5 minutes before expiry to prevent ungraceful server-side disconnections. - Extract token expiry time from GSR auth response - Implement token caching with automatic refresh - Schedule proactive reconnection before token expiry - Add comprehensive unit and integration tests - Update external-adapter-framework to 2.18.0 Fixes DF-26076
3425848 to
c2e1d64
Compare
The bump to 2.18.0 updated package.json but left the lockfile pinned at 2.17.1, so `yarn install --immutable` failed with YN0028 and every downstream check was skipped rather than run. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
aa834f1 to
1ed3b35
Compare
|
Internal images published from
|
|
Internal images published from
|
GitHub Actions
Failure
|
Internal images published from
|
|
Internal images published from
|
|
Internal images published from
|
1 participant
Summary
Fixes DF-26076: GSR adapter was experiencing hourly WebSocket disconnections (code=1006) followed by 504 errors for external operators.
Root cause: GSR issues 1-hour validity tokens, but the adapter was ignoring the token expiry timestamp and never refreshing. When GSR's server closed the connection at the 1-hour mark, reconnection attempts used the expired token and failed.
Changes
Testing