-
**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…
-
I am seeing multiple deal failures and `Graphysync ReceiveError` messages since the 1.5.0 upgrade. I have included a log snippet below.
I am not sure if this is a general issue or as a result of an…
-
-
At Infura, we have to deal with the occasional performance issue. Even though we now have added tracing in the HTTP handler of `go-ipfs-cmds` (not upstreamed yet, it's opentracing and you are aiming f…
-
### Checklist
- [X] This is **not** a question or a support request. If you have any lotus related questions, please ask in the [lotus forum](https://github.com/filecoin-project/lotus/discussions).
-…
-
### 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 is…
-
To support transfer resumption, a Graphsync requestor sends a `DoNotSendCids` message to the responder with ALL the CIDs received so far. This solution does NOT scale as sending ALL cids recieved for …
-
Currently, graphsync supports an extension for [`doNotSendCIDs`](https://github.com/ipfs/go-graphsync/blob/master/graphsync.go#L40), which provides a list of CIDs that should not be sent during a tran…
-
# What
Add an option to limit the number of in progress outgoing requests.
# Why
Currently, we have a limit on the number of incoming requests processed at the same time in the Responder impl…