Skip to content

Report unparseable objects in empty-expected responses as MalformedResponse - #702

Merged
jadamcrain merged 2 commits into
mainfrom
fix/malformed-empty-responses
Oct 23, 2026
Merged

jadamcrain merged 2 commits into
mainfrom
fix/malformed-empty-responses

Conversation

@jadamcrain

Copy link
Copy Markdown
Member

Extends #696 to the tasks that expect an empty response: empty-response, deadband and time sync WRITE responses whose objects can't be parsed now fail with MalformedResponse.

…edResponse

Empty-response, dead-band and time-sync WRITE tasks rejected any objects in
the response as UnexpectedResponseHeaders without parsing them. Like the
single-header tasks (#696), they now report objects that don't parse as
MalformedResponse with the cause. Objects that parse are still unexpected.
@jadamcrain
jadamcrain enabled auto-merge October 23, 2026 00:32
@jadamcrain
jadamcrain force-pushed the fix/malformed-empty-responses branch from 5fade44 to 10855d1 Compare October 23, 2026 00:32
@jadamcrain
jadamcrain force-pushed the fix/malformed-empty-responses branch from 10855d1 to 162f52b Compare October 23, 2026 00:32
@jadamcrain
jadamcrain added this pull request to the merge queue Oct 23, 2026
Merged via the queue into main with commit 914c7b9 Oct 23, 2026
36 checks passed
@jadamcrain
jadamcrain deleted the fix/malformed-empty-responses branch October 23, 2026 00:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant