-
Using Lotus markets version v1.11.3-rc1 graphsync v0.9.1 logs show these warnings during data transfers. It does not seem to affect the transfers.
2021-09-09T20:00:12.172Z WARN graphsync …
-
# What
Request allocation backpressure was thrown in quite ad-hoc to respond to miner concerns about memory usage. (as opposed to response allocation backpressure which has seen pretty careful deve…
-
Two racy tests showed up in https://github.com/ipfs/go-graphsync/pull/244:
* `TestValidationAndExtensions/test_update_hook_processing/can_send_extension_data/when_paused`
* `TestValidationAndExten…
rvagg updated
2 years ago
-
# What
Outgoing requests are now potentially not started at the same time they are requested
As a result, we may want a listener that higher level modules can register with to be notified when the…
-
We found a problem in go-data-transfer whereby when the node shuts down
- the context for all the outstanding requests are cancelled
- go-data-transfer's graphsync transport consumes all outstanding…
-
- @whyrusleeping initially reported this issue where Graphsync just freezes and all transfers come to a halt because they are waiting for memory on the buffer. Please see attached stack trace. Looks l…
-
When a graphsync transfer restarts (because the connection goes down, or because the node is bounced) the party receiving the data makes the same request, and uses an extension to indicate what data i…
-
**Describe the bug**
Lotus client doesn't use the right expiration date in PreCommit when sealing a sector and failed is the calculated expiration date is closed to 1555200
**Expected behavior…
-
### Checklist
- [X] This is **not** a security-related bug/issue. If it is, please follow please follow the [security policy](https://github.com/filecoin-project/lotus/security/policy).
- [X] This…
-
Some kind of race condition seems to be happening where from time to time, the last voucher sent over a network stream arrives before the acceptance voucher attached to the graphsync response.
See …