You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference/specifications/providers.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,12 +76,13 @@ The lifecycle is summarized below:
76
76
- for RPC providers, flags resolved with `reason=STATIC` are [cached](#caching)
77
77
- if flags change the associated stream (event or sync) indicates flags have changed, flush cache, or update `flag set` rules respectively and emit `PROVIDER_CONFIGURATION_CHANGED`
78
78
- if stream disconnects:
79
-
- attempt to [reconnect](#stream-reconnection) silently immediately
80
-
- if initial reconnect succeeds, do nothing
81
-
- if initial reconnect fails:
79
+
-[reconnect](#stream-reconnection) with backoff
80
+
- if reconnect attempt > `retryGraceAttempts`
82
81
- emit `PROVIDER_ERROR`
83
-
- RPC providers invalidate cache
84
-
- reconnect with backoff
82
+
- if reconnect attempt <= `retryGraceAttempts`
83
+
- emit `PROVIDER_STALE`
84
+
- RPC mode resolves `STALE` from cache where possible
85
+
- in-process mode resolves `STALE` from stored `flag set` rules
85
86
- on stream reconnection:
86
87
- emit `PROVIDER_READY` and `PROVIDER_CONFIGURATION_CHANGED`
87
88
- in-process providers store the latest `flag set` rules
0 commit comments