Skip to content
This repository has been archived by the owner on Jun 22, 2023. It is now read-only.

Fix client node error messages #123

Open
zavgorodnii opened this issue May 19, 2021 · 0 comments
Open

Fix client node error messages #123

zavgorodnii opened this issue May 19, 2021 · 0 comments
Assignees

Comments

@zavgorodnii
Copy link
Contributor

  1. Add more specific descriptions for message processing errors when possible (what happened? is it fatal)?
  2. Don't log errors that are logged when T of N messages are already consumed, and your FSM has already entered the next state — but T+1 message from the previous state arrives).
@zavgorodnii zavgorodnii assigned martelev and x88 and unassigned martelev May 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants