You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
appendToStream with expectedRevision -1 causes cryptic error #348
I get
Request message serialization failure: Cannot read property 'lo' of null
when attempting to appendToStream with -1 expectedRevision To Reproduce
Steps to reproduce the behavior:
call appendToStream with -1 expectedRevision
Expected behavior
A less cryptic error so the user can fix the issue
Actual behavior
A cryptic grpc error is thrown
Config/Logs/Screenshots
EventStore details
EventStore server version:
23.10.0
Operating system:
linux
EventStore client version (if applicable):
6.0.0 Additional context
The current version of NodeJS client doesn't allow setting -1 as the expected revision, cloud you clarify what you are actually doing? Also, server version 6.0.0 is confusing as it doesn't exist.
The current version of NodeJS client doesn't allow setting -1 as the expected revision, cloud you clarify what you are actually doing? Also, server version 6.0.0 is confusing as it doesn't exist.
Thanks for moving it, I forgot sorry.
Client version 6.0.0. Server version 23.10.0
I understand -1 is not a valid input but the types allow it and the error thrown is very hard to debug as an end user of the library.
Activity
rmp613 commentedon Nov 7, 2023
alexeyzimarev commentedon Nov 14, 2023
The current version of NodeJS client doesn't allow setting -1 as the expected revision, cloud you clarify what you are actually doing? Also, server version 6.0.0 is confusing as it doesn't exist.
riordanpawley commentedon Nov 14, 2023
Thanks for moving it, I forgot sorry.
Client version 6.0.0. Server version 23.10.0
I understand -1 is not a valid input but the types allow it and the error thrown is very hard to debug as an end user of the library.
w1am commentedon Nov 15, 2023
@riordanpawley This issue is already being addressed in this pull request #349
riordanpawley commentedon Nov 15, 2023
OK Happy to close then :)