Bitcoin full node and query server
Apr 17, 2026
View in context in the libbitcoin Slack #general mirror.
30 replies · neillm, evoskuil, pmienk · last Apr 17, 2026
evoskuil03:23
Got a couple macos green on network so I'll merge that, but my server PR will also have to clear. It may have a test failure still.
(edited)
neillm03:25
pmienk03:25
Okay... then i'll just pull get mine in as well - build scripts and such. but i've worked around this for the last six hours in some form and all other repos passed.
👍🏻 1
evoskuil03:28
The break came from a database update that server depends on. Server produced a build break before I could get it in, and that required an update to network. So that just cleared, and waiting on verification locally that server is good. 🙂
👍 1
evoskuil03:29
Neill got in before the database change, and Rowan and Phillip came in after..
(edited)😅 1
evoskuil03:30
12 years I've been fighting this. But now with more people hitting the repos again, it'll be good to mitigate it.
pmienk03:31
means we won't be exercising the install script's git clone actions for libbitcoin repos though
pmienk03:33
libbitcoin would be the 'owner', i believe that's the case with pr's as well, otherwise i'll need to spilt to two workflows. but can't confirm until test
🤔 1
evoskuil03:34
Lolz... check out the comments in the one test that's failing intermittently on macos:
// BUGBUG: macOS:
// Error codes have changed and the resulting race failure test is not matching expected code.
if (!result)
{
BOOST_CHECK_EQUAL(ec1, error::resolve_failed);
BOOST_CHECK_EQUAL(ec1, error::operation_canceled);
}evoskuil03:35
I'm getting an error code that's not either. I put this in there long ago so I could track it down.
evoskuil03:37
and I'm getting this...
[network:1 != ] [network:1 != &]
of course network::1 is just
network::error::unknown, which means it's a code coming the the OS that doesn't map to anything known.