-
**Describe the bug**
Dealmaking seems to be broken on the latest v1.9.0-rc5 version. The client does not connect to the miner.
**To Reproduce**
Steps to reproduce the behavior:
lotus client de…
-
### 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…
-
It's helpful when monitoring deals to know much of the data transfer block has completed. We have this information on the client side but are not exposing it in the UX.
Suggestion: Append a perce…
-
As we look forward to further evolution of the protocol, I'd like to reconsider the logic around whether we load blocks locally or remotely on the side making a request.
The high level summary of …
-
### 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…
-
https://github.com/ipfs/go-graphsync/runs/4514494584?check_suite_focus=true
```
graphsync_test.go:821:
Error Trace: tracing.go:123
graphsync_test.go:…
rvagg updated
2 years ago
-
The memory usage when creating client deals is very high. @jsign created 5 deals (40 GB total) which increased RAM usage by 15GB until transfers finished. Lotus total peak RAM usage = 40GB for these…
-
The advertisement entry processing logic is spread across two components:
* [`StorageWriteOpener`](https://github.com/filecoin-project/storetheindex/blob/09d121b7700e3c8557457173f807e1bf776267be/inte…
masih updated
2 years ago
-
# Goals
Now that we have basic request tracing, it would be really helpful to understand how incoming responses feed into traversals on the request side.
What we'd like is:
- record spans for t…
-
A miner node got OOM , due to too many transfers (had around 30+ incoming and not stalled, and 2 outgoing) coinciding with the miner doing wdPoSt, resulting in the miner losing all it's power.
As a…