Option to Reject requests by default#58
Merged
hannahhoward merged 3 commits intomasterfrom Apr 2, 2020
Merged
Conversation
Stebalien
requested changes
Mar 31, 2020
Member
Stebalien
left a comment
There was a problem hiding this comment.
Looks good except one case where you're not unlocking.
| for _, requestHook := range rm.requestHooks { | ||
| requestHook.hook(p, request, ha) | ||
| if ha.err != nil { | ||
| return |
cover case where unlocking was not happening
f904432 to
0d82d29
Compare
Stebalien
approved these changes
Apr 2, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Goals
Some graphsync operators may want to operate a graphsync node which is more locked down, rejecting all requests by default, and only authorizing requests through hooks.
Implementation