Raise loglevel of wrong expected version #10
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As this might well stall a system the log level should be higher.
|
@timbuchwaldt The latest Commanded version (master branch and recently published to Hex as v0.16.0-rc.0) includes a change (#132) to handle It now attempts to rebuild the aggregate state from the missing events and try to execute the command again. This will be retried up to ten times before an error is returned to command dispatch. Hopefully that should prevent the scenario from causing you an issue. I've merged you pull request. It will be included in the next release published to Hex (v0.5.0). |
slashdotdash
added a commit
that referenced
this pull request
Mar 13, 2018
|
Hey @slashdotdash - I saw, just working on integrating a git build to try that out, issue coming up regarding the current master state in a sec :P Thx! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As this might well stall a system the log level should be higher.
We have seen this issue kill our Commanded system completely as no new events were appended until we completely removed the stream from EventStore and restarted our application