< bitcoin-git> [gui] RandyMcMillan opened pull request #147: splash:bitcoin branding and cleanup (master...splash) https://github.com/bitcoin-core/gui/pull/147
< k3tan> i'm trying to spend coins that have already been spent but unconfirmed, it's an attack, can someone help?
< k3tan> i know this isn't the right forum to do so
< k3tan> but it's urgent if anyone is around
< bitcoin-git> [bitcoin] MarcoFalke pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/e98d1d674091...90ef622ab534
< bitcoin-git> bitcoin/master c5a8919 Pieter Wuille: Don't send 'sendaddrv2' to pre-70016 software
< bitcoin-git> bitcoin/master 1583498 Pieter Wuille: Send and require SENDADDRV2 before VERACK
< bitcoin-git> bitcoin/master 90ef622 MarcoFalke: Merge #20564: Don't send 'sendaddrv2' to pre-70016 software, and send befo...
< bitcoin-git> [bitcoin] MarcoFalke merged pull request #20564: Don't send 'sendaddrv2' to pre-70016 software, and send before 'verack' (master...202012_no_old_sendaddrv2) https://github.com/bitcoin/bitcoin/pull/20564
< wumpus> queip: in my exerpeince the main 'it seems stuck' issue is that GUI main thread hangs on block validation sometimes, due to lock contention, this can even cause some operating systems to pop up the 'has this program crashed' dialog, see also #17145
< gribble> https://github.com/bitcoin/bitcoin/issues/17145 | GUI event loop should be block free · Issue #17145 · bitcoin/bitcoin · GitHub
< wumpus> agree that the logging is sometimes too verbose too, though I'm fairly sure worrying peer behavior was all moved to the net category by now
< wumpus> the thing is also that some of the information is useful for troubleshooting. some level of misbehavior is perfectly normal on a P2P network, and it can (unlikely) happen that they get all misbehaving peers and thus no blocks, "not logging by default" would pretty much make us blind in trying to diagnose issues
< bitcoin-git> [bitcoin] MarcoFalke pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/90ef622ab534...a3586d592078
< bitcoin-git> bitcoin/master 7e9e7fe Carl Dong: qt/test: [FIX] Add forgotten Context setting in RPCNestedTests
< bitcoin-git> bitcoin/master 81137c6 Carl Dong: test: Add new ChainTestingSetup and use it
< bitcoin-git> bitcoin/master a3586d5 MarcoFalke: Merge #20323: tests: Create or use existing properly initialized NodeConte...
< bitcoin-git> [bitcoin] MarcoFalke merged pull request #20323: tests: Create or use existing properly initialized NodeContexts (master...2020-10-chainman-fixes) https://github.com/bitcoin/bitcoin/pull/20323
< wumpus> fanquake: nice, there was a githubdark firefox extension which i've used here and there, but yes it was about time they integrated it into the website i guess
< wumpus> in some places it draws a white circle behind my user icon in others the background is transparent as it should
< bitcoin-git> [bitcoin] MarcoFalke opened pull request #20606: Remove unused bits from service flags enum (master...2012-netServiceFlags) https://github.com/bitcoin/bitcoin/pull/20606
< wumpus> apart from that the dark theme is nice, imo, i'm ashamed to admit but i like Microsoft's recent style of visual design (also e.g. vscode)
< jonatack> yes, the new dark mode isn't bad, thought i liked the dark reader version too, hopefully with the extension disabled pages will load faster
< jonatack> though*
< promag> is is possible to make depends qt but don't erase the build?
< fanquake> promag: not quite sure what you mean?
< fanquake> as in make -C depends qt_built ?
< fanquake> That will stop building qt after the build stage
< wumpus> ohh that's good to have
< fanquake> yea you can do that with all the stages
< fanquake> i.e make -C depends libevent_configured
< fanquake> or make -C depends boost_preprocessed etc
< promag> ah nice
< promag> going to try that
< promag> just noticed at then end of depends/packages.md
< wumpus> i'd really like to get #20434 in, it seems ready and while it's not blocking me in any direct sense, it'd get th more controverial parts of #14066 out of the way so we can finally move forward with that
< gribble> https://github.com/bitcoin/bitcoin/issues/20434 | contrib: Parse ELF directly for symbol and security checks by laanwj · Pull Request #20434 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/14066 | gitian-linux: Build binaries for 64-bit POWER by luke-jr · Pull Request #14066 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] naumenkogs closed pull request #19843: Refactoring and minor improvement for self-advertisements (master...2020-08-refactor-advertiselocal) https://github.com/bitcoin/bitcoin/pull/19843
< bitcoin-git> [bitcoin] naumenkogs reopened pull request #19843: Refactoring and minor improvement for self-advertisements (master...2020-08-refactor-advertiselocal) https://github.com/bitcoin/bitcoin/pull/19843
< fanquake> wumpus: I've been meaning to look sorry
< fanquake> also reminds me to add the remaining symbol test for PE
< wumpus> not anyone's specific's fault but it's dragging on too long, three(?) major releases later and we still don't have powerpc binaries :)
< wumpus> fanquake: thanks!
< bitcoin-git> [bitcoin] fanquake pushed 5 commits to master: https://github.com/bitcoin/bitcoin/compare/a3586d592078...795afe6e63a1
< bitcoin-git> bitcoin/master a529fd3 John Newbery: [net processing] Move GetNodeStateStats into PeerManager
< bitcoin-git> bitcoin/master ed7e469 John Newbery: [net_processing] Move peer_map to PeerManager
< bitcoin-git> bitcoin/master a20ab22 John Newbery: [net processing] Make GetPeerRef const
< bitcoin-git> [bitcoin] fanquake merged pull request #19910: net processing: Move peer_map to PeerManager (master...2020-08-peer-plv2) https://github.com/bitcoin/bitcoin/pull/19910
< promag> fanquake: qt_staged deletes qt_built?
< promag> fanquake: nevermind, _staged removes extract_dir which contains build_dir :(
< promag> rebuild
< bitcoin-git> [bitcoin] fanquake opened pull request #20608: contrib: add symbol check test for PE binaries (master...symbol_check_test_pe) https://github.com/bitcoin/bitcoin/pull/20608
< bitcoin-git> [bitcoin] laanwj pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/795afe6e63a1...42ed7f51fafa
< bitcoin-git> bitcoin/master fa40168 MarcoFalke: Remove unused bits from service flags enum
< bitcoin-git> bitcoin/master 42ed7f5 Wladimir J. van der Laan: Merge #20606: Remove unused bits from service flags enum
< bitcoin-git> [bitcoin] laanwj merged pull request #20606: Remove unused bits from service flags enum (master...2012-netServiceFlags) https://github.com/bitcoin/bitcoin/pull/20606
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/42ed7f51fafa...7212db4d2a55
< bitcoin-git> bitcoin/master fa11110 MarcoFalke: util: Allow use of C++14 chrono literals
< bitcoin-git> bitcoin/master 7212db4 MarcoFalke: Merge #20602: util: Allow use of C++14 chrono literals
< bitcoin-git> [bitcoin] MarcoFalke merged pull request #20602: util: Allow use of C++14 chrono literals (master...2012-chronoLiterals) https://github.com/bitcoin/bitcoin/pull/20602
< promag> how do you interpret the eyes reaction on a comment?
< sipa> i interpret it as "surprised"
< sipa> i also don't think i've ever used it myself, so i may be off :)
< jonatack> promag: good question, idk either, sometimes it seems like "i'll have a look" and probably more often "surprised" like sipa says
< belcher_> iv seen it used as "im watching this / im interested"
< sipa> oh!
< sipa> that's a completely different interpretation
< jonatack> thanks! ambiguous is right
< promag> "taking look?"
< promag> I use it as "hmmmm ok ok ok ... hmmm nahh... hmmmm maybe .... later"
< promag> otherwise a comment sounds better right?
< pinheadmz> in my experience it means "huh, *someone* should take a look at this!" ... haha
< jonatack> The meeting log is up at https://bitcoincore.reviews/20477
< luke-jr> [18:20:08] <promag> how do you interpret the eyes reaction on a comment? <-- "N. was here, saw this, nothing to say"
< jonatack> ("meeting log is up" -> oops, wrong channel)
< sdaftuar> #19858 should be ready for merge -- it had 4 acks over a month ago -- but has needed a couple trivial rebases in the last two weeks
< gribble> https://github.com/bitcoin/bitcoin/issues/19858 | Periodically make block-relay connections and sync headers by sdaftuar · Pull Request #19858 · bitcoin/bitcoin · GitHub
< sdaftuar> if reviewers could verify the latest version of the code so that we can get this in i would appreciate it!
< bitcoin-git> [bitcoin] laanwj pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/7212db4d2a55...0038ce97584f
< bitcoin-git> bitcoin/master 90c0f26 MarcoFalke: Squashed 'src/crc32c/' changes from 224988680f..b5ef9be675
< bitcoin-git> bitcoin/master fa7c8d1 MarcoFalke: build: Update crc32c subtree
< bitcoin-git> bitcoin/master 0038ce9 Wladimir J. van der Laan: Merge #20603: build: Update crc32c subtree
< bitcoin-git> [bitcoin] laanwj merged pull request #20603: build: Update crc32c subtree (master...2012-crcSubtree) https://github.com/bitcoin/bitcoin/pull/20603
< ariard> bookmarked 19858 to review it again tmrw!
< bitcoin-git> [gui] luke-jr opened pull request #148: Bugfix: GUI: Restore SendConfirmationDialog button default to "Yes" (master...bugfix_gui_bumpyes) https://github.com/bitcoin-core/gui/pull/148
< bitcoin-git> [bitcoin] apoelstra opened pull request #20609: configure: output notice that test binary is disabled by fuzzing (master...2020-12--fuzz-config-output) https://github.com/bitcoin/bitcoin/pull/20609