[DB-287] Improve the error message when subscribing from an invalid position#3963
Conversation
hayley-jean
left a comment
There was a problem hiding this comment.
This error handling should also be added to the FilteredAllSubscription
DB-287 Unclear exception message when starting subscription far beyond starting point (EventStore.Core.TransactionLog.Chunks.TFChunk.InvalidReadException)
Describe the bug I ran into this on my development environment where I had deleted my event store docker container, but not the database where I store my checkpoints. From that point, my application wouldn't start anymore because the connection with ES was constantly failing. It took me quite some time to figure out what the problem was. Of course, resetting the checkpoints solves the issue, but a clearer error message would have given an indication. To Reproduce
Expected behavior Actual behavior EventStore details
|
42506c0 to
8c3672e
Compare
8c3672e to
75cda4e
Compare
75cda4e to
17a71dd
Compare
Fixed : #3195
Fixes : Improves the error message on the client side when a catch subscription is created from an invalid position. When the above mentioned exception was thrown, the error message on the client side was unclear stating "An exception was thrown by the handler", without specifying the actual error message, thus making it difficult to diagnose what the actual issue was. This PR improves the error message when the above issue is encountered.