Skip to content
This repository was archived by the owner on Mar 16, 2022. It is now read-only.

Fix empty streamed responses (for CRDT entities)#494

Merged
jroper merged 1 commit into
cloudstateio:masterfrom
pvlugter:empty-stream
Dec 3, 2020
Merged

Fix empty streamed responses (for CRDT entities)#494
jroper merged 1 commit into
cloudstateio:masterfrom
pvlugter:empty-stream

Conversation

@pvlugter
Copy link
Copy Markdown
Member

Resolves #493. Fix for this was simple: don't filter out empty client actions in UserFunctionRouter. We need a first empty response to always be sent downstream, otherwise an HttpResponse is never created due to waiting for the first response to extract metadata. Empty client actions will be filtered out in CommandHandler.processReplies instead.

Added tests to the TCK for this, including a proxy intercept test that has same behaviour as the presence example but using the CRDT TCK model entity.

@marcellanz, some updates to the CRDT TCK to include for Go support.

@marcellanz
Copy link
Copy Markdown
Contributor

@marcellanz, some updates to the CRDT TCK to include for Go support.

Thanks @pvlugter. I'll add them with cloudstateio/go-support#56 when this PR is merged I think.

@pvlugter pvlugter mentioned this pull request Nov 30, 2020
@jroper jroper merged commit bcbeaef into cloudstateio:master Dec 3, 2020
@pvlugter pvlugter deleted the empty-stream branch December 4, 2020 01:10
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Empty streamed responses are not actually connected

3 participants