2017-09-19

< bitcoin-git> bitcoin/master 4f7e37e Wladimir J. van der Laan: Merge #11307: wallet: Display non-HD error on first run...
< bitcoin-git> bitcoin/master fadf31e MarcoFalke: wallet: Display non-HD error on first run
< bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/1ab1b687cb58...4f7e37e26c5d
< bitcoin-git> [bitcoin] practicalswift closed pull request #11361: Remove redundant LOCK(…) and AssertLockHeld(…) (master...remove-redundant-locks) https://github.com/bitcoin/bitcoin/pull/11361
< bitcoin-git> bitcoin/master 1ab1b68 Wladimir J. van der Laan: doc: Add release notes for 0.15.0.1...
< bitcoin-git> [bitcoin] laanwj pushed 1 new commit to master: https://github.com/bitcoin/bitcoin/commit/1ab1b687cb5870258add2b08169cd974f08ed032
< bitcoin-git> [bitcoin] practicalswift opened pull request #11369: doc: Document locks - increase LOCK(...) comment coverage from 2 % to 77 % (master...lock-comments) https://github.com/bitcoin/bitcoin/pull/11369
< Duvdevan> and I'm banned from #bitcoin for unknown reasons... :/
< meshcollider> Duvdevan: this channel is only for discussion of bitcoin core development, to discuss altcoin development please use ##altcoin-dev
< mryandao> Duvdevan: #bitcoin probably better.
< Duvdevan> I'm fairly new into bitcoin
< bitcoin-git> [bitcoin] esotericnonsense opened pull request #11367: RPC: getblockchaininfo: Add disk_size, prune_target_size (master...2017-09-getblockchaininfo-addsize) https://github.com/bitcoin/bitcoin/pull/11367
< meshcollider> achow101: Any advice on https://github.com/bitcoin/bitcoin/blob/master/contrib/gitian-build.sh#L178-L184 ? Could they simply be removed?
< meshcollider> I wonder, is it because https://github.com/bitcoin/bitcoin/blob/master/doc/gitian-building.md#setting-up-debian-for-gitian-building uses br0 but the script tries to use lxcbr0 which doesn't exist?
< meshcollider> I had a similar issue, I gave up using the gitian-build.sh script and wrote a simple script of my own which basically follows the steps here: https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md#setup-and-perform-gitian-builds
< kallewoof> I don't really wanna waste anyone's time, but I've been trying to figure out the gitian build process lately and am having issues. I was following https://github.com/bitcoin/bitcoin/blob/master/doc/gitian-building.md and everything was fine down to "Getting and building the inputs". For one I had to cd into ../bitcoin/ for there to be a contrib/gitian-build.sh file (not mentioned, but no biggie),
< bitcoin-git> [bitcoin] esotericnonsense opened pull request #11366: Trivial: RPC/getblockchaininfo: pruneheight is only present in pruned mode (master...2017-09-getblockchaininfo-docs) https://github.com/bitcoin/bitcoin/pull/11366
< bitcoin-git> [bitcoin] mess110 closed pull request #11329: [test] Test abortrescan command (master...kallewoof/test-abort-rescan-2) https://github.com/bitcoin/bitcoin/pull/11329
< bitcoin-git> [bitcoin] anditto opened pull request #11365: [Tests] Add Qt GUI tests to Overview and ReceiveCoin Page (master...Adding-Qt-tests) https://github.com/bitcoin/bitcoin/pull/11365
< bitcoin-git> [bitcoin] azuchi closed pull request #11357: doc: Fix description of maximumCount (master...fix-0.15.0-release-notes) https://github.com/bitcoin/bitcoin/pull/11357
< bitcoin-git> [bitcoin] theuni opened pull request #11363: net: Split socket create connect (master...split-socket-create-connect) https://github.com/bitcoin/bitcoin/pull/11363

2017-09-18

< bitcoin-git> [bitcoin] gmaxwell opened pull request #11362: Remove nBlockMaxSize from miner opt struct as it is no longer used. (master...2017_09_rm_nBlockMaxSize) https://github.com/bitcoin/bitcoin/pull/11362
< gmaxwell> goatpig: if something like that went on for weeks it would be doubtful if bitcoin would continue to exist at the end of such an event, regardless tweaking forward assumevalid wouldn't be a high priority. ... losing it entirely isn't that big of a deal.
< jonasschnelli> cfields_: can you have a final look at https://github.com/bitcoin/bitcoin/pull/11113?
< bitcoin-git> [bitcoin] practicalswift opened pull request #11361: Remove redundant LOCK(…) and AssertLockHeld(…) (master...remove-redundant-locks) https://github.com/bitcoin/bitcoin/pull/11361
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #11323: mininode: add an optimistic write and disable nagle (master...optimistic-mininode) https://github.com/bitcoin/bitcoin/pull/11323
< bitcoin-git> bitcoin/master 4ce2f3d MarcoFalke: Merge #11323: mininode: add an optimistic write and disable nagle...
< bitcoin-git> bitcoin/master 1817398 Cory Fields: mininode: add an optimistic write and disable nagle...
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/44e1fd926cfb...4ce2f3d0d333
< sheldonthomas> bitcoin core cruising again.
< achow101> sheldonthomas: that will work. don't forget to remove that after you start Bitcoin Core otherwise you will be resetting those settings on every start
< sheldonthomas> Am going to add resetguisettings to my bitcoin.conf will that suffice?
< sheldonthomas> Just noticed I have another plist called org.bitcoinfoundation.Bitcoin-Qt.plist should I remove that?
< gribble> https://github.com/bitcoin/bitcoin/issues/11171 | RC2 Exits After Initialization · Issue #11171 · bitcoin/bitcoin · GitHub
< achow101> start Bitcoin Core with the -resetguisettings option
< sheldonthomas> I’m running it via a command in my path like: open /Applications/bitcoin15/Bitcoin-Qt.app/ --args -datadir=‘…’
< achow101> sipa: 0.15.0.1 is not released yet (no codesigned gitian builds yet, not posted to bitcoin.org)
< achow101> sheldonthomas: then start Bitcoin Core with -resetguisettings
< achow101> sheldonthomas: please pastebin the contents of ~/Library/Preferences/org.bitcoin.Bitcoin-Qt.plist
< gribble> https://github.com/bitcoin/bitcoin/issues/11171 | RC2 Exits After Initialization · Issue #11171 · bitcoin/bitcoin · GitHub
< sipa> sheldonthomas: please open an issue on https://github.com/bitcoin/bitcoin/issues
< gribble> https://github.com/bitcoin/bitcoin/issues/11116 | [script] Unit tests for script/standard and IsMine functions. by jimpo · Pull Request #11116 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/11113 | [net] Ignore getheaders requests for very old side blocks. by jimpo · Pull Request #11113 · bitcoin/bitcoin · GitHub
< andytoshi> RealM9: i am answering you in #bitcoin
< andytoshi> #bitcoin please
< RealM9> Bitcoin is again under a spam attack
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #11345: [tests] Check connectivity before sending in assumevalid.py (master...assume_valid_improvement) https://github.com/bitcoin/bitcoin/pull/11345
< bitcoin-git> bitcoin/master 44e1fd9 MarcoFalke: Merge #11345: [tests] Check connectivity before sending in assumevalid.py...
< bitcoin-git> bitcoin/master e9e9391 John Newbery: [tests] Check connectivity before sending in assumevalid.py...
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/d6d2c8503c40...44e1fd926cfb
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #11340: Trivial: Fix validation comments (master...patch-12) https://github.com/bitcoin/bitcoin/pull/11340
< bitcoin-git> bitcoin/master d6d2c85 MarcoFalke: Merge #11340: Trivial: Fix validation comments...
< bitcoin-git> bitcoin/master a0b4c24 Dan Raviv: Trivial: Fix validation comments...
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/e278f86c5369...d6d2c8503c40

2017-09-17

< bitcoin-git> [bitcoin] esotericnonsense opened pull request #11359: Add a pruning 'high water mark' to reduce the frequency of pruning events (master...2017-09-add-pruning-hwm) https://github.com/bitcoin/bitcoin/pull/11359
< gmaxwell> esotericnonsense: consider this, right now the chainstate on disk is 2.8gb adding the dbcache to the interval on syncing with defaults would end up with you needing to have 4GB free to sync bitcoin instead of 3.5.
< gribble> https://github.com/bitcoin/bitcoin/issues/11315 | Prune undermines the dbcache. · Issue #11315 · bitcoin/bitcoin · GitHub
< BashCo> achow101: -resetguisettings worked. Unfortunately I did that before looking for the plist file. :( I found the file though, called `org.bitcoin.Bitcoin-Qt.plist`.
< gribble> https://github.com/bitcoin/bitcoin/issues/11082 | Add new bitcoin_rw.conf file that is used for settings modified by this software itself by luke-jr · Pull Request #11082 · bitcoin/bitcoin · GitHub
< esotericnonsense> on linux it lives in .config/Bitcoin/Bitcoin-Qt.conf for me
< BashCo> removing the bitcoin.conf was the first thing I tried but no luck. my mac os 10.12 system didn't have any issues at all. It's still syncing, then I'll try the older system again. Bet -resetguisettings will fix it.
< luke-jr> jl2012: nCustomFeeRadio isn't in bitcoin.conf …
< achow101> BashCo: can you pastebin the contents of ~/Library/Preferences/bitcoin-qt.plist (or something like that I think)
< gribble> https://github.com/bitcoin/bitcoin/issues/11332 | Fix possible crash with invalid nCustomFeeRadio in QSettings (achow101, TheBlueMatt) by jonasschnelli · Pull Request #11332 · bitcoin/bitcoin · GitHub
< jl2012> BashCo: try removing bitcoin.conf. Should be fine
< bitcoin-git> [bitcoin] azuchi opened pull request #11357: Fix description of maximumCount (master...fix-0.15.0-release-notes) https://github.com/bitcoin/bitcoin/pull/11357
< meshcollider> Machine_Ex98: I already told you that this channel is for bitcoin core development, read the channel name and description, go to #bitcoin channel
< meshcollider> Take it to #bitcoin
< meshcollider> Machine_Ex98: That's offtopic in this channel, this channel is only for bitcoin core development
< CryptAxe> You don't have to ask on every channel.. And that's a companies API not the API of Bitcoin itself
< Machine_Ex98> We currently offer Bitcoin withdrawals and deposits on our website. Blockchain API is used to handle all operations.

2017-09-16

< bitcoin-git> [bitcoin] danra opened pull request #11354: Coins DB: Improve handling of FRESH child with non-DIRTY parent in CCoinsViewCa… (master...fix/batch-write-clean-parent-fresh-child) https://github.com/bitcoin/bitcoin/pull/11354
< bitcoin-git> [bitcoin] danra opened pull request #11353: Small refactor of CCoinsViewCache::BatchWrite() (master...refactor/coins-view-cache-batch-write) https://github.com/bitcoin/bitcoin/pull/11353
< bitcoin-git> [bitcoin] danra opened pull request #11351: Refactor: Modernize disallowed copy constructors/assignment (master...refactor/modernize-no-copy) https://github.com/bitcoin/bitcoin/pull/11351
< gribble> https://github.com/bitcoin/bitcoin/issues/11335 | Replace save|restoreWindowGeometry with Qt functions by MeshCollider · Pull Request #11335 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] laanwj closed pull request #11333: Use std::nth_element instead of std::sort to calculate median time past (master...improve/median-time-past) https://github.com/bitcoin/bitcoin/pull/11333
< bitcoin-git> [bitcoin] aijs closed pull request #11350: Merge pull request #1 from bitcoin/master (master...master) https://github.com/bitcoin/bitcoin/pull/11350
< bitcoin-git> [bitcoin] aijs opened pull request #11350: Merge pull request #1 from bitcoin/master (master...master) https://github.com/bitcoin/bitcoin/pull/11350
< bitcoin-git> [bitcoin] laanwj closed pull request #11196: Switch memory_cleanse implementation to BoringSSL's to ensure memory clearing even with -lto (master...fix-memory-clense) https://github.com/bitcoin/bitcoin/pull/11196
< bitcoin-git> bitcoin/master e278f86 Wladimir J. van der Laan: Merge #11196: Switch memory_cleanse implementation to BoringSSL's to ensure memory clearing even with -lto...
< bitcoin-git> bitcoin/master 1444c2e Adam Langley: Switch memory_cleanse implementation to BoringSSL's to ensure memory clearing even with link-time optimization....
< bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/09627b1dd41d...e278f86c5369
< bitcoin-git> [bitcoin] fanquake closed pull request #11347: 0.15 (master...0.15) https://github.com/bitcoin/bitcoin/pull/11347
< bitcoin-git> [bitcoin] aijs opened pull request #11347: 0.15 (master...0.15) https://github.com/bitcoin/bitcoin/pull/11347
< bitcoin-git> [bitcoin] fanquake closed pull request #11346: Merge pull request #1 from bitcoin/master (master...master) https://github.com/bitcoin/bitcoin/pull/11346
< bitcoin-git> [bitcoin] aijs opened pull request #11346: Merge pull request #1 from bitcoin/master (master...master) https://github.com/bitcoin/bitcoin/pull/11346

2017-09-15

< bitcoin-git> [bitcoin] jnewbery opened pull request #11345: [tests] Check connectivity before sending in assumevalid.py (master...assume_valid_improvement) https://github.com/bitcoin/bitcoin/pull/11345
< gribble> https://github.com/bitcoin/bitcoin/issues/10885 | Reject invalid wallets by promag · Pull Request #10885 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] isghe opened pull request #11343: added `-walletallowsymboliclink` (default false) (0.15...wallet-allow-symbolic-link) https://github.com/bitcoin/bitcoin/pull/11343
< bitcoin-git> [bitcoin] danra opened pull request #11342: Add sanity assert in CheckSequenceLocks (master...patch-13) https://github.com/bitcoin/bitcoin/pull/11342
< bitcoin-git> bitcoin/0.15 fb7b529 Wladimir J. van der Laan: doc: Release notes for 0.15.0.1...
< bitcoin-git> [bitcoin] laanwj pushed 1 new commit to 0.15: https://github.com/bitcoin/bitcoin/commit/fb7b5293844ea6adc5dcf5ad0a0c5890b4495939
< gribble> https://github.com/bitcoin/bitcoin/issues/11332 | Fix possible crash with invalid nCustomFeeRadio in QSettings (achow101, TheBlueMatt) by jonasschnelli · Pull Request #11332 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/11332 | Fix possible crash with invalid nCustomFeeRadio in QSettings (achow101, TheBlueMatt) by jonasschnelli · Pull Request #11332 · bitcoin/bitcoin · GitHub
< bitcoin-git> bitcoin/0.15 f266f26 Wladimir J. van der Laan: qt: Translations update pre-0.15.0.1...
< bitcoin-git> [bitcoin] laanwj pushed 1 new commit to 0.15: https://github.com/bitcoin/bitcoin/commit/f266f2668bf8fd73015bf8265f0d00f5e858b577
< bitcoin-git> [bitcoin] laanwj closed pull request #11341: [0.15.0] Bump manpages (0.15...Mf1709-docMan15) https://github.com/bitcoin/bitcoin/pull/11341
< gribble> https://github.com/bitcoin/bitcoin/issues/11338 | qt: Backup former GUI settings on `-resetguisettings` by laanwj · Pull Request #11338 · bitcoin/bitcoin · GitHub
< bitcoin-git> bitcoin/0.15 7123b95 Wladimir J. van der Laan: doc: Bump manpages to 0.15.0.1...
< bitcoin-git> bitcoin/0.15 8432332 Wladimir J. van der Laan: build: Bump version to 0.15.0.1...
< bitcoin-git> [bitcoin] laanwj pushed 2 new commits to 0.15: https://github.com/bitcoin/bitcoin/compare/46c8d23dad21...7123b95bea5b
< warren> Does bitcoin-cli have any tool that will tell you the feerate of a rawtx?
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #11339: Minor improvements to checkpoints code (master...refactor/checkpoints) https://github.com/bitcoin/bitcoin/pull/11339
< bitcoin-git> [bitcoin] MarcoFalke opened pull request #11341: [0.15.0] Bump manpages (0.15...Mf1709-docMan15) https://github.com/bitcoin/bitcoin/pull/11341
< gribble> https://github.com/bitcoin/bitcoin/issues/11338 | qt: Backup former GUI settings on `-resetguisettings` by laanwj · Pull Request #11338 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/11335 | Replace save|restoreWindowGeometry with Qt functions by MeshCollider · Pull Request #11335 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/11332 | Fix possible crash with invalid nCustomFeeRadio in QSettings (achow101, TheBlueMatt) by jonasschnelli · Pull Request #11332 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/10996 | [WIP] Add per-network config file network.conf by ajtowns · Pull Request #10996 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] danra closed pull request #11328: Move comment about transaction/block weight calculation (master...fix/weight-comment) https://github.com/bitcoin/bitcoin/pull/11328
< bitcoin-git> [bitcoin] danra closed pull request #11331: Trivial: Update outdated comment in validation.h (master...patch-11) https://github.com/bitcoin/bitcoin/pull/11331
< bitcoin-git> [bitcoin] danra opened pull request #11340: Trivial: Fix validation.cpp comment, BIP113 already deployed (master...patch-12) https://github.com/bitcoin/bitcoin/pull/11340
< meshcollider> supay venzen: this channel is only for discussion of bitcoin core, please take this discussion to another channel
< supay> on #bitcoin ali1234 mentioned that there are still analog holes
< meshcollider> supay: wrong channel, try #bitcoin
< bitcoin-git> [bitcoin] danra opened pull request #11339: Minor improvements to checkpoints code (master...refactor/checkpoints) https://github.com/bitcoin/bitcoin/pull/11339
< bitcoin-git> [bitcoin] laanwj opened pull request #11338: qt: Backup former GUI settings on `-resetguisettings` (master...2017_10_backup_resetguisettings) https://github.com/bitcoin/bitcoin/pull/11338
< wumpus> anyhow it doesn't really matter what the names are, as long as the names are unique within bitcoin-qt
< bitcoin-git> [bitcoin] laanwj closed pull request #11208: Fixing offscreen GUI issue (master...201709_offscreen_fix) https://github.com/bitcoin/bitcoin/pull/11208
< bitcoin-git> [bitcoin] danra opened pull request #11337: Fix code constness in CBlockIndex::GetAncestor() overloads (master...fix/const-get-ancestor) https://github.com/bitcoin/bitcoin/pull/11337
< bitcoin-git> bitcoin/0.15 46c8d23 Matt Corallo: Fix Qt 0.14.2->0.15.0 segfault if "total at least" is selected...
< bitcoin-git> [bitcoin] laanwj pushed 1 new commit to 0.15: https://github.com/bitcoin/bitcoin/commit/46c8d23dad216d990564014f4c8000b79fd36f4e
< bitcoin-git> [bitcoin] laanwj closed pull request #11332: Fix possible crash with invalid nCustomFeeRadio in QSettings (achow101, TheBlueMatt) (master...2017/09/qsettings_1) https://github.com/bitcoin/bitcoin/pull/11332
< bitcoin-git> bitcoin/master 09627b1 Wladimir J. van der Laan: Merge #11332: Fix possible crash with invalid nCustomFeeRadio in QSettings (achow101, TheBlueMatt)...
< bitcoin-git> bitcoin/master cdaf3a1 Matt Corallo: Fix Qt 0.14.2->0.15.0 segfault if "total at least" is selected...
< bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/ae233c4ec3d1...09627b1dd41d
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #11330: Trivial: Fix comments for DEFAULT_WHITELIST[FORCE]RELAY (master...patch-10) https://github.com/bitcoin/bitcoin/pull/11330
< bitcoin-git> bitcoin/master ae233c4 MarcoFalke: Merge #11330: Trivial: Fix comments for DEFAULT_WHITELIST[FORCE]RELAY...
< bitcoin-git> bitcoin/master dc2f737 danra: Trivial: Fix comments for DEFAULT_WHITELIST[FORCE]RELAY
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/0f399a9ff227...ae233c4ec3d1
< gmaxwell> your inside jokes might confuse people. :P fwiw, on an up to date debian testing system, which was QT4 only, you can parallel install QT5, but it seems bitcoin-qt still builds using QT4 even with QT5 'installed'.
< gribble> https://github.com/bitcoin/bitcoin/issues/9683 | random abort running master/HEAD · Issue #9683 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/11335 | [WIP] Replace save|restoreWindowGeometry with Qt functions by MeshCollider · Pull Request #11335 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] MeshCollider opened pull request #11335: [WIP] Replace save|restoreWindowGeometry with Qt functions (master...201709_fix_offscreen_2) https://github.com/bitcoin/bitcoin/pull/11335
< gmaxwell> Even if notepad is wrong (would be interesting to find out!) that still doesn't excuse bitcoin-- losing notepad is less serious then your wallet. :)
< gmaxwell> jonasschnelli: I explained before. If you increase your resolution, position there. Shut down bitcoin. Reduce resolution. You will be in this state.
< achow101> yes, from bitcoin.org
< luke-jr> bane5000: #bitcoin please
< luke-jr> bane5000: you mean prune=10000 ? note that user issues should be in #bitcoin though
< bane5000> i've restarted the bitcoin-qt, however, the old blocks do not seem to be disappearing, as my harddrive space has not been reduced
< bane5000> so i've enabled pruning on my core wallet (by creating bitcoin.conf in ~/.bitcoin/) and adding pruning=10000
< bitcoin-git> [bitcoin] achow101 opened pull request #11334: Remove custom fee radio group and remove nCustomFeeRadio setting (master...rm-nCustomFeeRadio) https://github.com/bitcoin/bitcoin/pull/11334
< gribble> https://github.com/bitcoin/bitcoin/issues/11208 | Fixing offscreen GUI issue by MeshCollider · Pull Request #11208 · bitcoin/bitcoin · GitHub

2017-09-14

< tloriato> sipa in which cases does the bitcoin wallet changes the i from the path?
< tloriato> oh, one more thing, sorry! bitcoin core uses m/0'/0'/k' for derivation path
< tloriato> Hello! I was looking for how I could import a BIP32 Extended Key into the Bitcoin Core wallet? I've tried the RPC Documentation but got no luck there.
< bitcoin-git> [bitcoin] danra opened pull request #11333: Use `std::nth_element` instead of `std::sort` to calculate median time past (master...improve/median-time-past) https://github.com/bitcoin/bitcoin/pull/11333
< esotericnonsense> actual url (wrong repo): https://github.com/bitcoin-dot-org/bitcoin.org/pull/1803
< gribble> https://github.com/bitcoin/bitcoin/issues/1803 | Apply MIT license to md2k7 art by luke-jr · Pull Request #1803 · bitcoin/bitcoin · GitHub
< luke-jr> ‎[21:11:33] ‎<‎dingus‎>‎ TYPO at the very top of https://bitcoin.org/en/release/v0.15.0 "14 October 2017" <- It's not October, yet, I hope
< esotericnonsense> from #bitcoin: dingus | TYPO at the very top of https://bitcoin.org/en/release/v0.15.0 "14 October 2017" <- It's not October, yet, I hope
< gribble> https://github.com/bitcoin/bitcoin/issues/11262 | bitcoin-qt segmentation fault · Issue #11262 · bitcoin/bitcoin · GitHub
< jonasschnelli> Okay. Retained authorship: https://github.com/bitcoin/bitcoin/pull/11332/commits
< jonasschnelli> BlueMatt: I'm trying to cherry-pick your https://github.com/bitcoin/bitcoin/commit/6ba2214e0fe57ecb9271819d2422ec44a9020a8d to keep you as author
< gribble> https://github.com/bitcoin/bitcoin/issues/11332 | Fix possible crash with invalid nCustomFeeRadio in QSettings by jonasschnelli · Pull Request #11332 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] jonasschnelli opened pull request #11332: Fix possible crash with invalid nCustomFeeRadio in QSettings (master...2017/09/qsettings_1) https://github.com/bitcoin/bitcoin/pull/11332
< morcos> usually with bitcoin.conf we don't change the meaning of the options (cough cough sipa)
< morcos> ha ha, fuzzing bitcoin.conf DEFINITELY breaks things
< wumpus> but as we're not even fuzzing bitcoin.conf settings yet
< jonasschnelli> could it happend by https://github.com/bitcoin/bitcoin/pull/10769?
< gmaxwell> I know that at least one of the users I helped during the RCs wasn't crashing (Because they had to kill bitcoin-qt in their task manager)
< gribble> https://github.com/bitcoin/bitcoin/issues/11171 | RC2 Exits After Initialization · Issue #11171 · bitcoin/bitcoin · GitHub
< harrymm> gmaxwell: not those you mentioned. i did try some other bitcoin python stuff at various times tho
< gmaxwell> harrymm: have you run bitcoin unlimited or bitcoin cash or likewise on that system you crashed on?
< gribble> https://github.com/bitcoin/bitcoin/issues/10663 | net: split resolve out of connect by theuni · Pull Request #10663 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/11089 | Enable various p2sh-p2wpkh functionality by luke-jr · Pull Request #11089 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/11167 | Full BIP173 (Bech32) support by sipa · Pull Request #11167 · bitcoin/bitcoin · GitHub
< wumpus> we managed to merge quite a lot during the coredev meet, so there's some place for new things in https://github.com/bitcoin/bitcoin/projects/8
< wumpus> #bitcoin-core-dev Meeting: wumpus sipa gmaxwell jonasschnelli morcos luke-jr btcdrak sdaftuar jtimon cfields petertodd kanzure bluematt instagibbs phantomcircuit codeshark michagogo marcofalke paveljanik NicolasDorier jl2012 achow101
< BlueMatt> oh, no, bitcoin-qt, sorry
< harrymm> wait. bitcoind or bitcoin-qt?
< harrymm> aww. should i have told gdb to load symbols from the symbols downloaded? it says it's reading them from bitcoin-qt (which doesn't have them)
< wumpus> can you pastebin the output of: <gmaxwell> harrymm: can you get a backtrace from it? gdb -c corefile ./path-to/bitcoin-qt then "thread apply all bt full"
< gmaxwell> harrymm: can you get a backtrace from it? gdb -c corefile ./path-to/bitcoin-qt then "thread apply all bt full"
< bitcoin-git> [bitcoin] danra opened pull request #11331: Trivial: Update outdated comment in validation.h (master...patch-11) https://github.com/bitcoin/bitcoin/pull/11331
< bitcoin-git> [bitcoin] jnewbery closed pull request #10748: [config] Help text cleanup (master...helptextcleanup) https://github.com/bitcoin/bitcoin/pull/10748
< gribble> https://github.com/bitcoin/bitcoin/issues/9774 | Enable host lookups for -proxy and -onion parameters by jmcorgan · Pull Request #9774 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/11171 | RC2 Exits After Initialization · Issue #11171 · bitcoin/bitcoin · GitHub
< achow101> if anyone sees any issue remotely like #11171, please get the GUI settings (from windows registry or from ~/.config/Bitcoin/Bitcoin-Qt.conf) before doing -resetguisettings
< bitcoin-git> [bitcoin] danra opened pull request #11330: Trivial: Fix comments for DEFAULT_WHITELIST[FORCE]RELAY (master...patch-10) https://github.com/bitcoin/bitcoin/pull/11330
< bitcoin-git> [bitcoin] mess110 opened pull request #11329: [test] Test abortrescan command (master...kallewoof/test-abort-rescan-2) https://github.com/bitcoin/bitcoin/pull/11329
< wumpus> if you think cloning bitcoin is bad, try cloning the linux kernel
< mryandao> has anyone here using tmux experience extreme lag when they `git clone` the bitcoin repo for the first time?
< bitcoin-git> [bitcoin] jnewbery closed pull request #10044: [tests] [build] Run functional tests in `make check` (master...reorg_makefiles) https://github.com/bitcoin/bitcoin/pull/10044
< bitcoin-git> [bitcoin] danra opened pull request #11328: Move comment about transaction/block weight calculation (master...fix/weight-comment) https://github.com/bitcoin/bitcoin/pull/11328
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #11326: Fix crash on shutdown with invalid wallet (master...201709_shutdown_crash) https://github.com/bitcoin/bitcoin/pull/11326
< bitcoin-git> bitcoin/master 0f399a9 MarcoFalke: Merge #11326: Fix crash on shutdown with invalid wallet...
< bitcoin-git> bitcoin/master 77939f2 MeshCollider: Fix uninitialized g_connman crash in Shutdown()
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/96d91b79bdfe...0f399a9ff227
< NicolasDorier> so actually I did not tried https://github.com/bitcoin/bitcoin/pull/11126 yet. But the path of the locks is different from the PR so I guess this is different error.
< bitcoin-git> bitcoin/master 96d91b7 Wladimir J. van der Laan: contrib: Ignore historical release notes for whitespace check...
< bitcoin-git> [bitcoin] laanwj pushed 1 new commit to master: https://github.com/bitcoin/bitcoin/commit/96d91b79bdfe1c0a58bd645f0f1d657caba16deb
< bitcoin-git> bitcoin/0.15 7c53587 Wladimir J. van der Laan: doc: Clean out release notes on 0.15 branch...
< bitcoin-git> [bitcoin] laanwj pushed 1 new commit to 0.15: https://github.com/bitcoin/bitcoin/commit/7c53587101eaf206a6a6a11a9398d43f139eadcf
< bitcoin-git> [bitcoin] laanwj closed pull request #11280: [0.15] Final to-do's for 0.15.0 release notes (0.15...201709_release_note_015_todo) https://github.com/bitcoin/bitcoin/pull/11280
< bitcoin-git> bitcoin/master 86700d3 Wladimir J. van der Laan: doc: add release-notes for 0.15.0 to master...
< bitcoin-git> [bitcoin] laanwj pushed 1 new commit to master: https://github.com/bitcoin/bitcoin/commit/86700d3d056caf54b091a6673dd6dabb65fac1f2
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #11300: Tests: Add a lint check for trailing whitespace (master...201709_whitespace_lint) https://github.com/bitcoin/bitcoin/pull/11300
< bitcoin-git> bitcoin/master f4ed44a MarcoFalke: Merge #11300: Tests: Add a lint check for trailing whitespace...
< bitcoin-git> bitcoin/master 1f379b1 MeshCollider: Add tab char lint check and exclude imported dependencies
< bitcoin-git> [bitcoin] MarcoFalke pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/7fcd61b2613c...f4ed44ab4a8f
< bitcoin-git> bitcoin/master dd36561 Evan Klitzke: Add a lint check for trailing whitespace....
< earlz> How exactly do you debug the bitcoin-qt on 64bit windows? I know the gitian builds produce both the binaries and debug symbols, but not sure what the best way to debug a crash is
< bitcoin-git> [bitcoin] MeshCollider opened pull request #11326: Fix crash on shutdown with invalid wallet (master...201709_shutdown_crash) https://github.com/bitcoin/bitcoin/pull/11326
< NicolasDorier> mmh I doubt the bug comes from bitcoin core actually
< gribble> https://github.com/bitcoin/bitcoin/issues/11316 | [qt] Add use available balance in send coins dialog by promag · Pull Request #11316 · bitcoin/bitcoin · GitHub
< NicolasDorier> Running bitcoin-core-0.15.0/test.rc3 on one of my server, getting "2017-09-14 06:55:48 socket send error The operation completed successfully. (0)" in logs _without_ debug=net. Then the connection drop to the peer. My peer is a NBitcoin peer, and I could not reproduce the error on the same 0.15.0/test.rc3 running on my machine.
< bitcoin-git> [bitcoin] fanquake closed pull request #11325: Corrected year (master...patch-1) https://github.com/bitcoin/bitcoin/pull/11325
< bitcoin-git> [bitcoin] OrfanMiner opened pull request #11325: Corrected year (master...patch-1) https://github.com/bitcoin/bitcoin/pull/11325

2017-09-13

< gribble> https://github.com/bitcoin/bitcoin/issues/11167 | Full BIP173 (Bech32) support by sipa · Pull Request #11167 · bitcoin/bitcoin · GitHub
< promag> can someone kick travis job https://travis-ci.org/bitcoin/bitcoin/jobs/275096269 ?
< gmaxwell> (I think expecting them to be well behaved is a bad idea, someone will spin up three pool daemons, they'll run in a fairly tight loop and prevent bitcoin from processing blocks, and wonder why they're getting orphan blocks)
< gribble> https://github.com/bitcoin/bitcoin/issues/10200 | Mining: Skip recent transactions if fee difference is small by sdaftuar · Pull Request #10200 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #10753: test: Check RPC argument mapping (master...2017_07_rpc_argument_check) https://github.com/bitcoin/bitcoin/pull/10753
< bitcoin-git> bitcoin/master 7fcd61b MarcoFalke: Merge #10753: test: Check RPC argument mapping...
< bitcoin-git> bitcoin/master 77aa9e5 Wladimir J. van der Laan: test: Check RPC argument mapping...
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/42973f834445...7fcd61b2613c
< bitcoin-git> [bitcoin] theuni opened pull request #11323: mininode: add an optimistic write and disable nagle (master...optimistic-mininode) https://github.com/bitcoin/bitcoin/pull/11323
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #10881: trivial: fix various pyflakes/vulture warnings (master...vulture) https://github.com/bitcoin/bitcoin/pull/10881
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #11078: [tests] Make p2p-leaktests.py more robust (master...p2p_leaktests_robust) https://github.com/bitcoin/bitcoin/pull/11078
< bitcoin-git> bitcoin/master 42973f8 MarcoFalke: Merge #11078: [tests] Make p2p-leaktests.py more robust...
< bitcoin-git> bitcoin/master 0063d2c John Newbery: [tests] Make p2p-leaktests.py more robust
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/8df48b36ed32...42973f834445
< harding> BashCo: that's an argument about what it is or is not possible to enforce. I think the important point is about what contributors to the Bitcoin Core project, mainly developers, choose to do regarding interactive communication.
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #11308: [qa] zapwallettxes: Wait up to 3s for mempool reload (master...Mf1709-qaZap3s) https://github.com/bitcoin/bitcoin/pull/11308
< bitcoin-git> bitcoin/master 8df48b3 MarcoFalke: Merge #11308: [qa] zapwallettxes: Wait up to 3s for mempool reload...
< bitcoin-git> bitcoin/master fadd0c1 MarcoFalke: [qa] zapwallettxes: Wait up to 3s for mempool reload
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/96ac26e56627...8df48b36ed32
< harding> BashCo: as I said above, I think the desire is not to get all Bitcoin users on the same platform; merely to get all developers on the same platform.
< BashCo> gmaxwell's meetup vid covering 0.15 was really popular. a 'sunday talk show' circuit covering various bitcoin media outlets could get a great response, but I understand it has the negative effect of placing devs on pedestals and creating PR spokesmen.
< BashCo> yeah fair enough. The Bitcoin community also has ambiguously defined boundaries. Lucky for Core, a large contingent of those communities support Core. That's why I think it's short sighted to pressure those communities to disband in favor of inferior platforms.
< luke-jr> BashCo: I don't agree. The latter is simply the Bitcoin community.
< OdaNobunaga> It's been suggested (today on the slack) to rebrand the slack into something not connected to core, for example "bitcoincommunity" or something like that (the bitcoin subdomain of slack is already taken)
< bitcoin-git> [bitcoin] mess110 closed pull request #11314: [tests] Add abortrescan RPC test (master...add-abortrescan-rpc-test) https://github.com/bitcoin/bitcoin/pull/11314
< BlueMatt> I absolutely agree there is some value in it, but some active steps should be taken to a) make clear this is not somehow a community related to bitcoin core (the technical project) and b) try to enforce lack of splitbrain
< achow101> s/the community/any bitcoin related discussion community/
< BlueMatt> while I understand the migration from Reddit and IRC to some extent, pushing folks towards Slack has, in large part, simply added yet another disconnected venue for Bitcoin discussion, creating yet another fork of the community whcih does not sufficiently communicate with other parts
< BlueMatt> and the "splitbrain community" issues greg raised are also critical here - as the Bitcoin community grows Bitcoin becomes harder to change, and thats good, but it should not do so needlessly simply because parts of the community do not sufficiently communicate with other parts
< bitcoin-git> [bitcoin] dooglus opened pull request #11320: Include the wallet name in log messages relating to wallets (master...wallet_name_in_log) https://github.com/bitcoin/bitcoin/pull/11320
< midnightmagic> He's over in #bitcoin too, last I checked.
< bitcoin-git> [bitcoin] sdaftuar opened pull request #11319: [qa] Fix error introduced into p2p-segwit.py, and prevent future similar errors (master...2017-09-fix-p2p-segwit) https://github.com/bitcoin/bitcoin/pull/11319
< BashCo_> The 'split communities' (IRC/Slack/Twitter/reddit/etc) are a simple reality that we have to come to terms with. Maybe it's unfortunate that 'Core' is in the Slack team name, but plain 'Bitcoin' is apparently being squatted. Even that would not solve anything since most people will still prefer Slack over IRC. /sorryforflood
< molz> gmaxwell, what would you suggest? you want to close the core slack and force everyone to join IRC? the only channel they can talk is #bitcoin but even that channel is not for everything one can discuss
< gmaxwell> molz: that kind of thing doesn't work, there are incredible misconceptions that come from just not talking. As far as never find it... http://webchat.freenode.net/?channels=bitcoin works pretty well for public chat.
< molz> gmaxwell, the Core slack has bridges to this channel and #bitcoin-dev, many people on the slack read these channels and more informed of what's going on with the development than you know, and if not for the slack, these people would never join IRC or know what's going on with the bitcoin development
< intcat> meanwhile people like me who prefer connecting to irc over tor so as to not expose IP to anyone lurking in bitcoin-related channels and suffering frequent disconnects as a result cant unfortunately follow all discussion here
< gmaxwell> Too bad hundreds of people never get to talk to me because they've been siphoned off into a Bitcoin Core chat group that I'm not in.
< gmaxwell> My interest in Bitcoin is primarily political, the same is true for (I assume) most of the technical contributors.
< gmaxwell> There are dozens of non-technical bitcoin channels on IRC-- ones that also get participation from many of the longest standing bitcoin users and technical contributors too.
< gmaxwell> By splitting the community I mean creating a parallel and seperate Bitcoin Core chat community and directing traffic there instead of where the actual bitcoin project people are.
< CodeShark> using the name was because otherwise what am I promoting? for better or worse, the Bitcoin Core project was where the greatest protocol expertise was concentrated
< CodeShark> I have invested FAR more of my time promoting Bitcoin Core than Ciphrex in the last two years
< CodeShark> I'll be totally blunt here - I deeply respect your domain knowledge and breadth of understanding and have learned tremendously from you...but I also strongly disagree with the public relations strategy the Bitcoin Core project had a couple years ago
< CodeShark> about the best option we had to keep the network together is to help promote the Bitcoin Core project since it is by far the most responsible and most reliable when it comes to avoiding consensus failures
< gmaxwell> As far as I am concerned: It is the _bitcoin project_. As far as I am concerned there is no bitcoin core project. Bitcoin Core is a piece of software.
< CodeShark> for better or worse, it all sort of concentrated around the Bitcoin Core project because that's where the best protocol experts were
< CodeShark> I could have used my company name instead to promote crap - but I wanted to help the Bitcoin Core project. this isn't about me
< gmaxwell> The software project here is the _bitcoin_ project, Bitcoin core is the name of the reference client, it's not the only thing the project does.
< CodeShark> but not everyone agrees on what Bitcoin is
< gmaxwell> OdaNobunaga: the whole thing is the _fking_ bitcoin project, dude. Bitcoin.
< OdaNobunaga> CodeShark: Perhaps we should come up with a word to refer to the "decentralisation first"/user-driven/cypherpunk movement within bitcoin, and rename the slack after it
< OdaNobunaga> I agree with gmaxwell, it's hard to see what the slack has to do with bitcoin core
< CodeShark> I see the Bitcoin Core software project as part of a wider movement
< gmaxwell> please get bitcoin core's name off it before doing anything else with moderation... so tired of being blamed for moderation actions in stuff we have no control over.
< gmaxwell> many of the developers are usually in #bitcoin.
< OdaNobunaga> On the Slack we kind of call that the "user driven" bitcoin (I've seen that being used a few times)
< CodeShark> I would like to give a name to the movement that favors the conservative approach to consensus rule changes and general avoidance of incompatibilities unless the technical benefits greatly outweigh the costs...and to distinguish it from the Bitcoin Core FOSS project
< OdaNobunaga> But the I've been surprised to see it being called "the bitcoin core slack" as the discussion there mostly isn't technical, and its biggest contributors aren't core devs
< OdaNobunaga> I've been following the various the "bitcoin core" slack on a daily basis (mostly its various UASF channels) since last March, and I think that there's a lot of amplification going on, but at the same time the most vocal contributors there are well aware that they're an extreme minority and that they can't possibly have everything go their way; I w
< gmaxwell> For example, one of your top contributors (who sent me some very nasty remarks) told me that Bitcoin Core was _never_ going to force a segwit activation and so BIP148 was the _only_ option.
< CodeShark> I just wanted to build good products atop bitcoin and decided to support the Bitcoin Core project however I could because it's the most stable, most reliable, most secure implementation of validation and relay
< CodeShark> I believe #bitcoin-core-dev should focus more on tech developments and code. we have other channels for things like media strategy
< CodeShark> I just saw Bitcoin Core viciously attacked a couple years ago and hostile parties form...and did whatever I could to communicate basic principles. it's impossible to get everyone aligned on all the details, but the priority was around trying to at least have a coherent overarching message
< CodeShark> I try my best to keep abreast of important developments within Bitcoin Core and do my best to communicate them
< sipa> sure, but why does that need to happen under the "Bitcoin Core" name?