Vlad
Vlad
@omritoptix This error handling is a bit tricky. First error [here](https://github.com/celestiaorg/go-cnc/pull/59/files#diff-4b667feae66c9d46b21b9ecc19e8958cf4472d162ce0a47ac3e8386af8bbd8cfR65) is networking client error, and if it happens, there will be no response value returned. The second error [here](https://github.com/celestiaorg/go-cnc/pull/59/files#diff-4b667feae66c9d46b21b9ecc19e8958cf4472d162ce0a47ac3e8386af8bbd8cfL67)...
@Wondertan Good question. Breaking changes in range APIs require updates across all integrations. If any integration misses the migration window, we risk production issues. We will migrate all other methods...
CI for doc gen failed due to previous step of go-releaser failing. Reference: https://github.com/celestiaorg/celestia-node/actions/runs/11256100269 Error from CI: ⨯ release failed after 8m19s error=scm releases: failed to publish artifacts: failed to...
This is great idea and should help to improve quality of bootstraper service and also make it easy for anyone to launch one. We can separate trusted peers config from...
Just a heads-up: we’re in the middle of a major refactor of the Shrex client/server (see [#4249](https://github.com/celestiaorg/celestia-node/pull/4249)). Once that lands, most of the current code will be replaced, so we...
As for solution, if you will be still interested in contributing after the refactoring, please take a look into setting up appropriate stream timeout, that should match parent context timeout...
Just a quick add-on: If we move the Pruner interface to the same package as Availability, there’s a another benefit. Availability could be aware of the pruner settings and skip...
Hey @ptdatta! It has been a while since you opened this PR. Are you interested in updating it, to make it up to date with main?
It should instead be a metric on the pruner. DASer is unaware of where or whether the latest pruned height is. In fact, it already exists as `prnr_last_pruned` (the pruner's...
Current metrics seems sufficient. If not, new issue is needed