-
Currently, selectors lookup and explore iteratively. Unfortunately, this means we often have to pause while going to disk.
Instead, we should be reading from disk in parallel. The simplest approach…
-
Currently, we have an implementation of requestor pausing that works as follows:
- Requestor can be paused in a block hook or a imperatively (calling PauseRequest on graphsync with a request ID)
- "…
-
# Context
Crashing inputs were discovered while fuzzing the go-graphsync [`DecodeMetadata`](https://github.com/LeastAuthority/go-graphsync/blob/master/metadata/metadata.go#L23) function. Some of thes…
-
# What
The basic architecture of the request and response manager is as follows: all public methods put messages into a buffered channel that is processed sequentially by an internal thread. (see …
-
Currently, when we render data transfer status, the bytes sent on the side of the party sending data advances extremely quickly.
With the new BlockSentListener hook in graphsync, it should be possi…
-
A `Request()` returns a channel that gives you all of the _Nodes_ of a DAG traversal, rather than the _Blocks_ of that traversal.
In datatransfer, I see that it’s just doing a `for range req.respon…
rvagg updated
2 years ago
-
When a party queues a transfer due to throttling policies (e.g. Graphsync simultaneous transfers), the other party doesn't come to know. All they see is a stalled "ongoing" transfer.
We should add …
raulk updated
2 years ago
-
I was reading: https://github.com/filecoin-project/specs/blob/master/network-protocols.md and saw there is a BlockSync section
Currently, go-filecoin does not support BlockSync cause it uses GraphS…
-
This is now our next highest transfer error after #120. But it's also new. Discovered last week, validated here with https://github.com/application-research/autoretrieve/pull/121 and turned from a sil…
-
### Checklist
- [X] This is **not** a question or a support request. If you have any boost related questions, please ask in the [discussion forum](https://github.com/filecoin-project/boost/discussion…