feat: update lassie to sync Retriever (after provider rewrite revert) #173
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.
This is #167 but against current
master
, i.e. with the provider rewrite reverted.It's using filecoin-project/lassie#54 as the "latest" lassie, because that's the newest incarnation of the interface - taking a linkSystem per retrieval.
Unfortunately this won't build because there's a dependency problem involving the infamous btcd breaking change .. and I don't have the patience today to figure out which bit broke that, maybe the go-data-transfer upgrade? It was working with in #167 with a version of lassie that's not too far off this one.