Bitcoin full node and query server

Sep 19, 2026

View in context in the libbitcoin Slack #general mirror.

Also, concurrency restrictions have been leveed upon CI builds. Currently in libbitcoin at most one action per pull request is queued - the last build is active, others are canceled upon last build creation. I've additionally limited personal repositories to a single active action per branch, with the same cancelation behavior

5 replies · pmienk, evoskuil · last Sep 19, 2026

pmienk16:53

Again, open to feedback, suggested improvements, etc

evoskuil17:50

I've already found this very helpful. Just have to be careful to delay push if you want to differentiate potentially failing builds, but generally it's better to just keep queuing up the commits and the build stays at the top, instead of grinding through what is then a stack of irrelevance.

pmienk17:51

Yeah, and if you ever want to backtrack to locate a failure introduction you can always stop the top and manually trigger the rebuild.

👍🏻 1

pmienk18:13

BTW, merge does cancel pull request CI now, but it does it by generating a noop action. I'll look into making that one appear as canceled sometime as to not he misleading.

pmienk18:14

But unless there's an issue I'm moving back to version instead of process fixes

👍🏻 1