-
Notifications
You must be signed in to change notification settings - Fork 38
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
Feat/use neo-go 0.106.3 features #2907
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2907 +/- ##
==========================================
+ Coverage 23.66% 23.70% +0.03%
==========================================
Files 774 774
Lines 44887 44818 -69
==========================================
- Hits 10623 10622 -1
+ Misses 33418 33349 -69
- Partials 846 847 +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.
lux gut
2e6d3ce
to
857dbd8
Compare
Adopting neo-go new waiting API functionality. It is a little functional change in the NewEpoch event handling (deposit was sent but not awaited), but it should not be a disadvantage: a silent sending without waiting can confuse when reading logs. `morph/client/Client.Wait` was also dropped as not used. Signed-off-by: Pavel Karpy <[email protected]>
Context is an important part of neo-go client's lifecycle, it is passed at creation stage. Do not use `context.Background`, use a general application one instead. Signed-off-by: Pavel Karpy <[email protected]>
`Reverse` explains it worse that explicit `LE`. Signed-off-by: Pavel Karpy <[email protected]>
857dbd8
to
939766a
Compare
neofs-adm is not touched to save mental health (#2905 was left). Closes #2902.