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

Investigate and fix possible client-node related exceptions leakage into node-node processing #1492

Open
skhoroshavin opened this issue Aug 10, 2020 · 0 comments
Open

Investigate and fix possible client-node related exceptions leakage into node-node processing #1492

skhoroshavin opened this issue Aug 10, 2020 · 0 comments
Labels
discussing Under further discussion.

Comments

@skhoroshavin
Copy link
Contributor

When investigating issue in Sovrin StagingNet (detail can be found here: https://sovrin.atlassian.net/browse/SN-18) it turned out some nodes were sending INSTANCE_CHANGE messages with suspicion code 110 and comment "could not authenticate". This is actually an exception from client-facing part of code and should never be caught by node-to-node processing.

Acceptance criteria

  • Investigate and fix issue
@WadeBarnes WadeBarnes added the discussing Under further discussion. label Jun 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussing Under further discussion.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@skhoroshavin @WadeBarnes