chore: Finish goodbye handling. #130
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note
Low Risk
Low risk: primarily adds logging and threads a
reasonstring throughGOODBYEstatus results; behavior changes are limited to observability and an extra status field.Overview
FDv2
GOODBYEhandling now captures and exposes the server-provided reason end-to-end:FDv2SourceResult.Statusadds areasonfield (withgetReason()), andFDv2SourceResult.goodbye()now stores that reason instead of discarding it.Both polling (
PollingBase) and streaming (StreamingSynchronizerImpl) paths now log an info message when agoodbyeis received and pass the extracted reason intoFDv2SourceResult.goodbye(...). Tests are updated to assertreasonis null for non-goodbye statuses and equals the expected string for goodbye events.Written by Cursor Bugbot for commit b20c3c4. This will update automatically on new commits. Configure here.