Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Projection Management grpc GetStateAsync vs http api behavior difference #142

Open
ylorph opened this issue Aug 6, 2021 · 0 comments
Open

Projection Management grpc GetStateAsync vs http api behavior difference #142

ylorph opened this issue Aug 6, 2021 · 0 comments
Assignees
@thefringeninja
Labels
bug Something isn't working subsystem/projections

Comments

@ylorph
Copy link
Contributor

ylorph commented Aug 6, 2021 •
edited

Describe the bug

  • GetStateAsync fails while the HTTP Api does not when a projection state is returned.
  • Http Api GET projection/{name}/state might return an empty result, the GetStateAsync operation fails in such cases
    The excetpion is System.Text.Json.JsonReaderException

To Reproduce
Steps to reproduce the behavior:
the code in this gist reproduces the error when there is a state returned by the HTTP Api : https://gist.github.com/ylorph/a27997621b3e6e26e635223c30714912

Expected behavior
GetStateAsync should return the data when it is available
GetStateAsync should not fail when there is no data to return

Actual behavior
GetStateAsync fails with an expection in all cases

EventStore details

  • EventStore server version: 21.6
  • EventStore client version (if applicable): 21.2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@thefringeninja thefringeninja

Labels
bug Something isn't working subsystem/projections
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@thefringeninja @oskardudycz @ylorph