-
Notifications
You must be signed in to change notification settings - Fork 17
feat: MaxLinks for pulls #374
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
Conversation
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.
My biggest concern is a transport option that only works one direction, with no indicator to that effect. I think the right thing is to update graphsync PR to go both directions, and then incorporate that here.
5a31334
to
99ba9d3
Compare
Failures discussed in #373, they come from the diff between go-graphsync v0.14.0 and the current |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #374 +/- ##
==========================================
+ Coverage 61.28% 61.31% +0.02%
==========================================
Files 30 30
Lines 3180 3200 +20
==========================================
+ Hits 1949 1962 +13
- Misses 1002 1009 +7
Partials 229 229
|
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.
LGTM
* feat: use traversal link budget instead of limitstore Ref: ipfs/go-graphsync#420 Ref: filecoin-project/go-data-transfer#374 * chore(deps): update go-data-transfer v2.0.0-rc7 * style(lint): fix fmt --------- Co-authored-by: hannahhoward <[email protected]>
Uses ipfs/go-graphsync#420
Further comments in Lassie