-
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
adm: use native neo-go sessions in dump-hashes
#2224
adm: use native neo-go sessions in dump-hashes
#2224
Conversation
Codecov Report
@@ Coverage Diff @@
## support/v0.35 #2224 +/- ##
=================================================
- Coverage 30.89% 30.87% -0.03%
=================================================
Files 383 383
Lines 28365 28387 +22
=================================================
Hits 8764 8764
- Misses 18854 18876 +22
Partials 747 747
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
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.
Nice.
} | ||
|
||
if !bytes.HasSuffix(bs, []byte(zone)) { | ||
continue | ||
return |
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.
If we had lots of domains in one zone, `dump-hashes` for all others can miss some domains, because we need to restrict ourselves with _some_ number. In this commit we use neo-go sessions by default, with a proper failback to in-script iterator unwrapping. Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com>
If we had lots of domains in one zone,
dump-hashes
for all others can miss some domains, because we need to restrict ourselves with some number.In this commit we use neo-go sessions by default, with a proper failback to in-script iterator unwrapping.
Signed-off-by: Evgenii Stratonikov e.stratonikov@yadro.com