Commit 89821fe
committed
fix: reset highestObservedSequence on no-progress replay to prevent unbounded retry loop
When replay makes no progress, highestObservedSequence was left at its
stale high-water mark, causing resolveReplayNeedAfterRecovery to
permanently return shouldReplay: true. This created an infinite 100ms
polling loop with no escape.
Reset highestObservedSequence to latestSequence when replay makes no
progress so stale observations don't drive infinite retries. Fresh live
events will re-set it via classifyDomainEvent if genuinely needed.1 parent 5c18bad commit 89821fe
File tree
2 files changed
+6
-3
lines changed- apps/web/src
2 files changed
+6
-3
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
65 | 65 | | |
66 | 66 | | |
67 | 67 | | |
68 | | - | |
| 68 | + | |
69 | 69 | | |
70 | 70 | | |
71 | 71 | | |
| |||
75 | 75 | | |
76 | 76 | | |
77 | 77 | | |
78 | | - | |
| 78 | + | |
79 | 79 | | |
80 | 80 | | |
81 | 81 | | |
82 | | - | |
| 82 | + | |
83 | 83 | | |
84 | 84 | | |
85 | 85 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
130 | 130 | | |
131 | 131 | | |
132 | 132 | | |
| 133 | + | |
| 134 | + | |
| 135 | + | |
133 | 136 | | |
134 | 137 | | |
135 | 138 | | |
| |||
0 commit comments