Skip to content

Tags: osmosis-labs/cometbft

Tags

v0.38.17-v28-osmo-1

Toggle v0.38.17-v28-osmo-1's commit message
fix: peer mock interface

v0.38.15-v27-osmo-2

Toggle v0.38.15-v27-osmo-2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
fix: copy TxIndex TxBytes value (#150)

* fix: copy TxIndex TxBytes value

* chore: changelog

v0.38.15-v27-osmo-1

Toggle v0.38.15-v27-osmo-1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
fix: merge error (#149)

v0.38.12-v27-osmo-1

Toggle v0.38.12-v27-osmo-1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore: add changelog v27 0.38.12 (#146)

v0.38.12-v26-osmo-2

Toggle v0.38.12-v26-osmo-2's commit message
chore: update CHANGELOG for final v26 osmosis-labs/cometbft

v0.38.12-v26-osmo-1

Toggle v0.38.12-v26-osmo-1's commit message
Merge remote-tracking branch 'upstream/v0.38.x' into osmo/v0.38.12

v0.38.11-v26-osmo-1

Toggle v0.38.11-v26-osmo-1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore: adding changelog (#144)

* chore: adding changelog

* chore: add last parts to changelog

v0.37.4-v25-osmo-12

Toggle v0.37.4-v25-osmo-12's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
feat(p2p): render `HasChannel(chID)` is a public `p2p.Peer` method (#… (

#128)

* feat(p2p): render `HasChannel(chID)` is a public `p2p.Peer` method (cometbft#3510)

Closes: cometbft#3472

It also prevents reactors from starting routines intended to send
messages to a peer that does not implement/support a given channel.
Because all `Send()` or `TrySend()` calls from this routine will be
useless, always returning `false` and possibly producing some busy-wait
behavior (see cometbft#3414).

The changes are restricted to: mempool and evidence reactor, because
they use a single channel and have a sending routine peer peer, and two
of the consensus routines, for Data and Votes.

Block and State sync reactors have smarter ways to deal with
unresponsive peers, so probably this check is not needed.

---

- [x] Tests written/updated
- [x] Changelog entry added in `.changelog` (we use
[unclog](https://github.com/informalsystems/unclog) to manage our
changelog)
- [x] Updated relevant documentation (`docs/` or `spec/`) and code
comments
- [x] Title follows the [Conventional
Commits](https://www.conventionalcommits.org/en/v1.0.0/) spec

* One more test fix

* Add changelog

* Update changelog

---------

Co-authored-by: Daniel <daniel.cason@informal.systems>

v0.37.4-v25-osmo-11

Toggle v0.37.4-v25-osmo-11's commit message
changelog

v0.37.4-v25-osmo-10

Toggle v0.37.4-v25-osmo-10's commit message
More proper fix