-
Notifications
You must be signed in to change notification settings - Fork 37
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.
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
ir: Do not create new notary requests for SN netmap entrances #2717
ir: Do not create new notary requests for SN netmap entrances #2717
Conversation
4eee5b0
to
5d26195
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #2717 +/- ##
==========================================
- Coverage 28.78% 28.78% -0.01%
==========================================
Files 415 415
Lines 32388 32378 -10
==========================================
- Hits 9324 9319 -5
+ Misses 22230 22224 -6
- Partials 834 835 +1 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It certainly fixes #830. Contracts can be improved, but gradually and in a separate issue, we need to ensure only one method is called for at least a release and then we can remove the other one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i'd prefer to not embody commit by issues only. Text and other commit refs are more reliable, issue refs complement
5d26195
to
4c77cd2
Compare
After fb13ef9, it is now possible not to create an additional notary request but to sign the original one. See also nspcc-dev/neofs-contract#324 that includes SN in a netmap with `AddPeer` netmap call only (without the formly required `AddPeerIR` call). Closes #830. Signed-off-by: Pavel Karpy <[email protected]>
4c77cd2
to
511f7a2
Compare
See #2612, nspcc-dev/neofs-contract#324. Refs #830.