<bitcoin-git>
[bitcoin] furszy opened pull request #29913: bugfix: update chainman best_header after block reconsideration (master...2024_fix_reconsiderblock_bestheader) https://github.com/bitcoin/bitcoin/pull/29913
VonNaturAustreVe has joined #bitcoin-core-dev
VonNaturAustreVe has quit [Client Quit]
VonNaturAustreVe has joined #bitcoin-core-dev
VonNaturAustreVe has quit [Changing host]
VonNaturAustreVe has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
bitdex has quit [Ping timeout: 260 seconds]
brunoerg_ has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 268 seconds]
VonNaturAustreVe has quit [Quit: Leaving]
BrandonOdiwuor has quit [Ping timeout: 250 seconds]
brunoerg_ has quit [Ping timeout: 268 seconds]
abubakarsadiq has joined #bitcoin-core-dev
ion- has quit [Remote host closed the connection]
ion- has joined #bitcoin-core-dev
ion- has quit [Remote host closed the connection]
<josie>
git status
<fanquake>
nothing to commit, working tree clean
<josie>
if only that were true...
<sipa>
git push upstream -d master
preimage has joined #bitcoin-core-dev
jonatack has joined #bitcoin-core-dev
ion- has joined #bitcoin-core-dev
<josie>
sipa: that's certainly one way to fix all the bugs
brunoerg has joined #bitcoin-core-dev
bugs_ has joined #bitcoin-core-dev
brunoerg has quit [Remote host closed the connection]
brunoerg has joined #bitcoin-core-dev
<_aj_>
mightn't fix all the bugs, but should remove any merge conflicts?
ion- has quit [Ping timeout: 260 seconds]
ion- has joined #bitcoin-core-dev
ion- has quit [Ping timeout: 268 seconds]
ion- has joined #bitcoin-core-dev
BrandonOdiwuor has joined #bitcoin-core-dev
ion- has quit [Ping timeout: 268 seconds]
ion- has joined #bitcoin-core-dev
ion- has quit [Remote host closed the connection]
ion- has joined #bitcoin-core-dev
ion- has quit [Remote host closed the connection]
ion- has joined #bitcoin-core-dev
ion- has quit [Remote host closed the connection]
preimage has quit [Ping timeout: 240 seconds]
preimage has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] glozow closed pull request #29827: test: p2p: add test for rejected tx request logic (`m_recent_rejects` filter) (master...202404-test-p2p-check_rejected_tx_requests) https://github.com/bitcoin/bitcoin/pull/29827
the_mariner has quit [Ping timeout: 256 seconds]
the_mariner has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] instagibbs opened pull request #29915: test: Don't fetch orphan parent when parent is in orphanage (master...2024-04-parent_orphan_orphan_nofetch) https://github.com/bitcoin/bitcoin/pull/29915
the_mariner has quit [Ping timeout: 268 seconds]
___nick___ has joined #bitcoin-core-dev
jonatack has quit [Ping timeout: 260 seconds]
jonatack has joined #bitcoin-core-dev
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 256 seconds]
jon_atack has joined #bitcoin-core-dev
jonatack has quit [Ping timeout: 268 seconds]
preimage has quit [Quit: WeeChat 4.2.2]
<roasbeef>
so we're seeing some weird behavior on testnet with bitcoin nodes, iiuc ppl are mining a ton of empty blocks, and occasionally we get an error that: ConnectBlock(): coinbase pays too much (actual=26389831 vs limit=26389830)
<roasbeef>
we've tried to reindex (mentioned as a solution in that issue), but then it still ends up choking on blocks later
<roasbeef>
yes
<roasbeef>
this is bitciond 26
<achow101>
Try 27?
<sipa>
without a way to reproduce this is hard to investigate
<roasbeef>
hehe these are connected to lnd nodes, and bitcoind 27 added breaking behavior in sendrawtransaction so we can't update those yet (we have v0.17.5 staged, should drop shortly), but thought this was exceptional enough that I should dig into it
<achow101>
my testnet node handled that block fine
<achow101>
but it is 27.99
<sipa>
i'm spinning up a 26.0 on testnet
<achow101>
roasbeef: any chance of a coredump?
<roasbeef>
lemmie see
<sipa>
if it's reproducible after a restart, perhaps the datadir is useful to have
<achow101>
(may contain keys and other private data, blah blah, share privately if you care)
<roasbeef>
they're running in k8s, so the container can be wiped/re-created pretty quickly (re obtaining a core dump), can try to extract the state to run it on a normal host also
<roasbeef>
the datadir is persistent tho
<roasbeef>
just testnet, no wallet instance
<sipa>
roasbeef: if you restart bitcoind, does it immediately/quickly segfault again?
<roasbeef>
after restart it'll go back to processing blocks to catch up, then will hit a problematic block and repeat the cycle