-
## Bug Report
### Setup
Ci, per #2387
**Environment**:
ci
**node command runtime flags**:
ci
### Config
ci
### What happened?
split -d -n l/20 /home/runner/work/cometbft…
-
https://github.com/cometbft/cometbft/pull/2765#discussion_r1568503909
`types/block.go`:
```go
MaxCommitSigBytes int64 = 131 + 10 // where's the 10 from?
```
## Definition of done
- [ ]…
-
problem: the cometbft mempool does not remove txs from the mempool until it sees that it was included in a block (ok or failed). however, due to including only successful txs in a block via `prepare_p…
noot updated
2 months ago
-
Channel multiplexing:
- [ ] #3250
- [ ] #2128
- [ ] #2954
Connection's performance:
- [ ] #2951
- [x] #2958
- [ ] #2956
- [x] #2988
- [ ] #3197
- [ ] #3198
Marshalling:
- [ ] #31…
-
Idgaf this is happening p0.
-
There should be documentation for the deficiencies where CometMock does not replicate the behaviour of CometBFT (yet).
For example, a folder with Markdown documentation.
-
Please feel free to edit this issue
https://github.com/cometbft/cometbft/actions/runs/7396653794/job/20122263666?pr=1954
```log
--- FAIL: TestNodeDelayedStart (2.01s)
node_test.go:138:
…
-
### Problem
The current `TestGetBlock` function in `full_client_test.go` does not thoroughly test the Block RPC call according to the CometBFT [documentation](https://docs.cometbft.com/v0.38/spec/rp…
-
## Feature Request
### Problem Definition / Summary
Osmosis has been working on reducing block times as a result of recent performance improvements. The current approach involves overwriting…
-
We have had multiple instances where changes to the `sequencer` state machine result in a validator failing to reach consensus with the rest of the nodes after it crashes and goes into a second round …