< wangchun> what are ANCESTOR/DESCENDANT limits? My tx failed the test.
< sdaftuar> wangchun: starting in 0.12, there are limits on the length of unconfirmed transaction chains. "ancestors" refers to all the unconfirmed transactions that a given transaction depends on
< sdaftuar> wangchun: "descendants" refer to the unconfirmed transactions that depend on a given one
< sdaftuar> these limits apply to mempool acceptance of new transactions
< sdaftuar> default is 25/25 if i remember correctly
< wangchun> sdaftuar: my tx has only one ancestor, but it is refused
< wangchun> sdaftuar: which limit should I increase?
< sdaftuar> that can't be the ancestor/descendant limits unless you manually overrode the default
< sdaftuar> what's the exact error?
< wangchun> too-long-mempool-chain
< sdaftuar> oh, it could be the size of the transaction i suppose
< sdaftuar> how big is it?
< wangchun> sdaftuar: I was trying to send another tx which only has one vin = b28fe214a938921dcbf39146b806ab954c77f81e0b58ac4e4d8c5e9f21a308fa:0 but it has about 5000 vouts
< wangchun> at the time I was trying to send, b28fe214a938921dcbf39146b806ab954c77f81e0b58ac4e4d8c5e9f21a308fa hasn't been confirmed
< sdaftuar> wangchun: ok, yes i forgot to mention that in addition to limits on the number of ancestors and descendants, there are also limits on the size of a transaction including ancestors and size of a transaction including descendants
< wangchun> I already raised standard tx size limit to 500kb
< wangchun> so should i increase these new limits too?
< sdaftuar> yes, you can try -limitancestorsize=500 and -limitdescendantsize=500
< sdaftuar> those values are interpreted as kb
< sdaftuar> and default to 101
< wangchun> the tx itself is counted in ancestor/descendant size?
< wangchun> ancestor or descendant?
< sdaftuar> i would bump both to be safe
< sdaftuar> i'm double-checking the calculation
< sdaftuar> both numbers include the transaction itself
< sdaftuar> so if it has one unconfirmed parent, make sure that you set -limitancestorsize to be large enough for both transactions
< wangchun> sdaftuar: ok
< GitHub3> [bitcoin] sdaftuar opened pull request #7367: Mention mempool chain limits in release notes (0.12...update-release-notes) https://github.com/bitcoin/bitcoin/pull/7367
< GitHub55> [bitcoin] sdaftuar opened pull request #7368: [Tests] Eliminate race condition in mempool_packages.py (master...fix-package-test) https://github.com/bitcoin/bitcoin/pull/7368
< phantomcircuit> wangchun, why are you trying to send 5000 vouts? that seems like a lot
< phantomcircuit> morcos, did you work on improving the utxo caching setup to avoid clearing it on flush?
< michagogo> .whois cfields cfields
< michagogo> er
< michagogo> sorry
< wangchun> phantomcircuit: daily payout
< phantomcircuit> wangchun, you dont have a minimum payout amount of > $1 ?
< wangchun> phantomcircuit: our threshold is 0.001 BTC
< wangchun> that about ¥2.51
< wangchun> s/that/that's/
< phantomcircuit> wangchun, not even enough to buy a candy bar :P
< adnn_> The Classic fork will be successful. This is looking like the end.
< GitHub91> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/fd9356ba4eb5...f2cf071e702f
< GitHub91> bitcoin/master 4d10d2e Suhas Daftuar: Eliminate race condition in mempool_packages test
< GitHub91> bitcoin/master f2cf071 Wladimir J. van der Laan: Merge pull request #7368...
< GitHub95> [bitcoin] laanwj closed pull request #7368: [Tests] Eliminate race condition in mempool_packages.py (master...fix-package-test) https://github.com/bitcoin/bitcoin/pull/7368
< GitHub135> [bitcoin] laanwj pushed 1 new commit to 0.12: https://github.com/bitcoin/bitcoin/commit/1488fc8eac3ab8ed58d84c6bd61b5295b01de295
< GitHub135> bitcoin/0.12 1488fc8 Suhas Daftuar: Eliminate race condition in mempool_packages test...
< GitHub191> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/f2cf071e702f...2350ab28fb8c
< GitHub191> bitcoin/master bd34174 Prayag Verma: Update license year range to 2016
< GitHub191> bitcoin/master 2350ab2 Wladimir J. van der Laan: Merge pull request #7363...
< GitHub8> [bitcoin] laanwj closed pull request #7363: Update license year range to 2016 (master...patch-1) https://github.com/bitcoin/bitcoin/pull/7363
< GitHub8> [bitcoin] laanwj pushed 1 new commit to 0.12: https://github.com/bitcoin/bitcoin/commit/098fcb56945fa6e445f8585890cf935825ffd079
< GitHub8> bitcoin/0.12 098fcb5 Prayag Verma: Update license year range to 2016...
< GitHub12> [bitcoin] laanwj pushed 2 new commits to 0.12: https://github.com/bitcoin/bitcoin/compare/098fcb56945f...8b7a0f88cb91
< GitHub12> bitcoin/0.12 2e552b0 Suhas Daftuar: Mention mempool chain limits in release notes
< GitHub12> bitcoin/0.12 8b7a0f8 Wladimir J. van der Laan: Merge pull request #7367...
< GitHub144> [bitcoin] laanwj closed pull request #7367: Mention mempool chain limits in release notes (0.12...update-release-notes) https://github.com/bitcoin/bitcoin/pull/7367
< GitHub121> [bitcoin] laanwj closed pull request #7347: Release notes about mining code changes (0.12...rnfixes2) https://github.com/bitcoin/bitcoin/pull/7347
< GitHub21> [bitcoin] laanwj pushed 2 new commits to 0.12: https://github.com/bitcoin/bitcoin/compare/8b7a0f88cb91...b0cb0556737b
< GitHub21> bitcoin/0.12 5cacb8f Alex Morcos: Add comment about mining changes and more about priority
< GitHub21> bitcoin/0.12 b0cb055 Wladimir J. van der Laan: Merge pull request #7347...
< GitHub94> [bitcoin] laanwj pushed 8 new commits to 0.12: https://github.com/bitcoin/bitcoin/compare/b0cb0556737b...1709cc5cb0e5
< GitHub50> [bitcoin] laanwj closed pull request #7338: Backports for 0.12.0 (updated to e289807) (0.12...backports-for-0.12.0) https://github.com/bitcoin/bitcoin/pull/7338
< GitHub94> bitcoin/0.12 6092ff2 Suriyaa Kudo: Set link from http:// to https://...
< GitHub94> bitcoin/0.12 6307beb Patrick Strateman: Note that reviewers should mention the commit hash of the commits they reviewed....
< GitHub94> bitcoin/0.12 6191a9b Jonas Schnelli: [RPC-Tests] add option to run rpc test over QT clients...
< GitHub33> [bitcoin] laanwj pushed 2 new commits to 0.12: https://github.com/bitcoin/bitcoin/compare/1709cc5cb0e5...d04525a065ae
< GitHub33> bitcoin/0.12 fa8c497 MarcoFalke: [doc] backwards-compatibility issues due to chainstate obfuscation
< GitHub168> [bitcoin] laanwj closed pull request #7345: [0.12] Add backwards-compatibility issues (chainstate obfuscation) to release notes (0.12...Mf1601-docObfuscation) https://github.com/bitcoin/bitcoin/pull/7345
< GitHub33> bitcoin/0.12 d04525a Wladimir J. van der Laan: Merge pull request #7345...
< GitHub153> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/2350ab28fb8c...a8bd616fea62
< GitHub153> bitcoin/master 9d263bd Chris Wheeler: Typo fixes in comments
< GitHub153> bitcoin/master a8bd616 Wladimir J. van der Laan: Merge pull request #7329...
< GitHub44> [bitcoin] laanwj closed pull request #7329: Trivial: fix typo (master...typofix) https://github.com/bitcoin/bitcoin/pull/7329
< GitHub182> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/a8bd616fea62...5e00147838b0
< GitHub182> bitcoin/master 0331aa3 calebogden: Fixing typos on security-check.py and torcontrol.cpp
< GitHub182> bitcoin/master 5e00147 Wladimir J. van der Laan: Merge pull request #7313...
< GitHub58> [bitcoin] laanwj closed pull request #7313: [trivial] fixing multiple typos (master...patch-1) https://github.com/bitcoin/bitcoin/pull/7313
< GitHub151> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/5e00147838b0...3ec5bb0a6e2c
< GitHub151> bitcoin/master 7777994 MarcoFalke: [qa] Fix pyton syntax in rpc tests
< GitHub151> bitcoin/master 3ec5bb0 Wladimir J. van der Laan: Merge pull request #7335...
< GitHub161> [bitcoin] laanwj closed pull request #7335: [qa] Fix pyton syntax in rpc tests (master...Mf1601-rpcSyntax) https://github.com/bitcoin/bitcoin/pull/7335
< GitHub0> [bitcoin] laanwj pushed 1 new commit to 0.12: https://github.com/bitcoin/bitcoin/commit/d8b062d752838aa0d7141355a1341768d4c4064c
< GitHub0> bitcoin/0.12 d8b062d MarcoFalke: [qa] Fix pyton syntax in rpc tests...
< GitHub88> [bitcoin] laanwj pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/3ec5bb0a6e2c...b8f485c47284
< GitHub88> bitcoin/master fa4f4b6 MarcoFalke: Add clang-format-diff.py from the LLVM svn...
< GitHub88> bitcoin/master fa074a6 MarcoFalke: [contrib] Prepare clang-format-diff for usage
< GitHub88> bitcoin/master b8f485c Wladimir J. van der Laan: Merge pull request #7304...
< GitHub71> [bitcoin] laanwj closed pull request #7304: [contrib] Add clang-format-diff.py (master...Mf1601-clang-format-diff) https://github.com/bitcoin/bitcoin/pull/7304
< GitHub156> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/b8f485c47284...d3dfc6d7e18e
< GitHub156> bitcoin/master fa1cb1a MarcoFalke: [qa] Test walletpassphrase timeout
< GitHub156> bitcoin/master d3dfc6d Wladimir J. van der Laan: Merge pull request #7320...
< GitHub88> [bitcoin] laanwj closed pull request #7320: [qa] Test walletpassphrase timeout (master...Mf1601-rpcWalletPass) https://github.com/bitcoin/bitcoin/pull/7320
< GitHub119> [bitcoin] laanwj closed pull request #7060: build: Make networking work inside LXC builder in gitian-building.md (master...2015_11_gitian_building) https://github.com/bitcoin/bitcoin/pull/7060
< GitHub39> [bitcoin] laanwj reopened pull request #7060: build: Make networking work inside LXC builder in gitian-building.md (master...2015_11_gitian_building) https://github.com/bitcoin/bitcoin/pull/7060
< GitHub69> [bitcoin] laanwj pushed 5 new commits to master: https://github.com/bitcoin/bitcoin/compare/d3dfc6d7e18e...c851d8d71b2e
< GitHub69> bitcoin/master fac11ea MarcoFalke: [init] Fix error message of maxtxfee invalid amount
< GitHub69> bitcoin/master fa6ab96 MarcoFalke: [init] Add missing help for args
< GitHub69> bitcoin/master faa572a MarcoFalke: [init] Help Msg: Use Params(CBaseChainParams::MAIN)
< GitHub129> [bitcoin] laanwj closed pull request #7290: [init] Add missing help for args (master...Mf1601-doc) https://github.com/bitcoin/bitcoin/pull/7290
< GitHub71> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/c851d8d71b2e...47c5ed19f3ba
< GitHub71> bitcoin/master 64360f1 Wladimir J. van der Laan: Make max tip age an option instead of chainparam...
< GitHub71> bitcoin/master 47c5ed1 Wladimir J. van der Laan: Merge pull request #7208...
< GitHub60> [bitcoin] laanwj closed pull request #7208: Make max tip age an option instead of chainparam (master...2015_12_maxtipage) https://github.com/bitcoin/bitcoin/pull/7208
< michagogo> wumpus: I don't suppose you have any clue why the OS X gitian build is failing so spectacularly?
< MarcoFalke> michagogo. 0.11.2 works fine?
< michagogo> Yep, I build 0.11.2 on this setup and 0.12.0rc1 windows and Linux are fine
< michagogo> And fanquake also had the same failure
< michagogo> built*
< GitHub177> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/47c5ed19f3ba...ae20172941ff
< GitHub177> bitcoin/master 94bdd71 Gregory Sanders: Added help text for chainwork value
< GitHub177> bitcoin/master ae20172 Wladimir J. van der Laan: Merge pull request #7232...
< GitHub101> [bitcoin] laanwj closed pull request #7232: [RPC] getblock: Added help text for chainwork value (master...getblockhelp) https://github.com/bitcoin/bitcoin/pull/7232
< GitHub56> [bitcoin] laanwj pushed 1 new commit to 0.12: https://github.com/bitcoin/bitcoin/commit/c0d2382170962ecae72fd90d4830fcadd4c2ed30
< GitHub56> bitcoin/0.12 c0d2382 Gregory Sanders: Added help text for chainwork value...
< GitHub54> [bitcoin] laanwj pushed 4 new commits to master: https://github.com/bitcoin/bitcoin/compare/ae20172941ff...e4e77ee55d8a
< GitHub54> bitcoin/master 16d4fce James O'Beirne: Add assert_is_hex_string and assert_is_hash_string to RPC test utils.
< GitHub54> bitcoin/master 4745636 James O'Beirne: Add RPC documentation for getblockheader[chainwork].
< GitHub54> bitcoin/master 135d6ec James O'Beirne: Add RPC tests for getblockheader.
< GitHub73> [bitcoin] laanwj closed pull request #7194: Fix help, add RPC tests for getblockheader (master...test_getblockheader) https://github.com/bitcoin/bitcoin/pull/7194
< GitHub99> [bitcoin] laanwj pushed 1 new commit to 0.12: https://github.com/bitcoin/bitcoin/commit/351ffd8482ff812e6b464c870bb4b0bff85e3884
< GitHub99> bitcoin/0.12 351ffd8 James O'Beirne: Fix help, add RPC tests for getblockheader...
< michagogo> wumpus: Yeah, that's not it. It's the build itself that's crashing and burning, not the signer.
< michagogo> It looks like it might be happening at the qt stage -- deps build seems fine until that point, but then something breaks in a really weird way
< MarcoFalke> Can you downgrade gitian-builder to something older (e.g. 29c406e1174) and test again?
< MarcoFalke> (Needs new base images)
<@wumpus> MarcoFalke, it's just the OSX build that is failing, if it was a base image problem wouldn't all the builds fail?
< MarcoFalke> wumpus have you been using the latest gitian builder version for the OSX build?
<@wumpus> michagogo: no, no clue, I had some problems with LXC myself hence https://github.com/bitcoin/bitcoin/pull/7060 , but haven't heard anyone else about it (and shouldn't be macosx specific either)
<@wumpus> MarcoFalke, yes
<@wumpus> but I use KVM, not LXC
< michagogo> wumpus: fanquake was having the same issue, also using LXC, and also only on the OS X build
<@wumpus> so yes I also have issues with LXC all the time
< michagogo> wumpus: and also, that PR is for networking, I'm preseeding the cache as mentioned in release-process
< michagogo> wumpus: idk, it mostly works for me, until something weird happens like this
< michagogo> Definitely not "all the time"
<@wumpus> the PR is not only networking, it also adds some packages that I needed
<@wumpus> (or maybe those are only networking related, I dunno)
<@wumpus> do you have a log of what goes wrong?
< michagogo> ca-certificates is definitely only networking
< michagogo> that's toget the deps over https
< michagogo> and, er...
< michagogo> the image should already have *python*...
< michagogo> yeah, it's in scrollback
< michagogo> one sec
< michagogo> wumpus: so somehow build.log is being truncated:
< michagogo> I used `script` to capture a tailf of the log: https://www.dropbox.com/s/uwdejt9rczbywuq/macbuild.log?dl=0
<@wumpus> /usr/bin/env: python: No such file or directory
<@wumpus> make: *** [dist/Bitcoin-Qt.app/Contents/MacOS/Bitcoin-Qt] Error 127
<@wumpus> what did you say about python? :p
< michagogo> ...what.
<@wumpus> I don't think python is part of the LXC image at all, and it's necesary for macosx build
< michagogo> um.
< michagogo> What changed between 0.11 and 0.12 to make it necessary?
< michagogo> one sec, lemme run on-target dpkg -l | grep python
<@wumpus> ... or maybe it's just not part of the LXC iimage as 'python', but e.g. python2?
<@wumpus> in most places we explicitly call it python2
<@wumpus> but I don't think that's the problem, package 'python' installs python 2
< michagogo> Looks like we only have python3
< michagogo> But that leaves 2 questions. First, why is it only needed for OS X and not for Linux or Windows?
< michagogo> And second, why is it required in 0.12 when it isn't in 0.11?
< michagogo> The descriptor diff doesn't look like it could be related
< * michagogo> checks the depends/ diff
< michagogo> Okay, lets try...
< michagogo> wumpus: btw, why does that PR add python to all the descriptors?
< GitHub176> [bitcoin] MarcoFalke opened pull request #7370: [0.12] Doc: Wallet & Pruning (0.12...Mf1601-docWalletPrune) https://github.com/bitcoin/bitcoin/pull/7370
< GitHub152> [bitcoin] MarcoFalke opened pull request #7371: [0.12] backports (0.12...Mf1601-012Backports) https://github.com/bitcoin/bitcoin/pull/7371
<@wumpus> michagogo, never narrowed it down further
< GitHub126> [bitcoin] laanwj closed pull request #7360: Fix osslsigncode patch url (master...doc-fix) https://github.com/bitcoin/bitcoin/pull/7360
< GitHub27> [bitcoin] MarcoFalke opened pull request #7372: Trivial: [qa] wallet: Print maintenance (master...Mf1601-qaWalletPrint) https://github.com/bitcoin/bitcoin/pull/7372
< GitHub186> [bitcoin] sdaftuar opened pull request #7373: [Tests] Fix error in blockchain.py introduced in merge (master...fix-blockchain-py) https://github.com/bitcoin/bitcoin/pull/7373
< MarcoFalke> or maybe just cancel all running pulls other than the one from sdaftuar. They will fail anyway
< MarcoFalke> wumpus ?
<@wumpus> is there a big red button to just cancel everything?
< MarcoFalke> idk
< MarcoFalke> It is only the 4 running on https://travis-ci.org/bitcoin/bitcoin/pull_requests
<@wumpus> cool, travis has a command line tool
< MarcoFalke> Nice, but you canceled https://travis-ci.org/bitcoin/bitcoin/builds/103118874
< MarcoFalke> This one should run ;)
< MarcoFalke> or get merged
<@wumpus> yes I'm cancelling everything, as said
< GitHub101> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/e4e77ee55d8a...e2ed57e61e44
< GitHub101> bitcoin/master 4a04879 Suhas Daftuar: Fix error in blockchain.py introduced in merge
< GitHub101> bitcoin/master e2ed57e Wladimir J. van der Laan: Merge pull request #7373...
< GitHub56> [bitcoin] laanwj closed pull request #7373: [Tests] Fix error in blockchain.py introduced in merge (master...fix-blockchain-py) https://github.com/bitcoin/bitcoin/pull/7373
< GitHub166> [bitcoin] laanwj pushed 1 new commit to 0.12: https://github.com/bitcoin/bitcoin/commit/51af87f0786d3a0c9fbff84a9648781138ab84c3
< GitHub166> bitcoin/0.12 51af87f Suhas Daftuar: Fix error in blockchain.py introduced in merge...
< GitHub133> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/e2ed57e61e44...21376af183ff
< GitHub133> bitcoin/master facd288 MarcoFalke: [qa] wallet: Print maintenance
< GitHub133> bitcoin/master 21376af Wladimir J. van der Laan: Merge pull request #7372...
< GitHub182> [bitcoin] laanwj closed pull request #7372: Trivial: [qa] wallet: Print maintenance (master...Mf1601-qaWalletPrint) https://github.com/bitcoin/bitcoin/pull/7372
< GitHub117> [bitcoin] laanwj pushed 2 new commits to 0.12: https://github.com/bitcoin/bitcoin/compare/51af87f0786d...cda064caa13e
< GitHub117> bitcoin/0.12 fa31133 MarcoFalke: [Doc] Wallet & Pruning
< GitHub95> [bitcoin] laanwj closed pull request #7370: [0.12] Doc: Wallet & Pruning (0.12...Mf1601-docWalletPrune) https://github.com/bitcoin/bitcoin/pull/7370
< GitHub117> bitcoin/0.12 cda064c Wladimir J. van der Laan: Merge pull request #7370...
< PRab> FYI, I've been running 0.12RC1 and maxuploadtarget appears to be working.
< PRab> I think thats a great improvement over the previous QOS setup I had.
< MarcoFalke> but maxuploadtarget isn't doing qos
< PRab> Its not, but my goal is to limit it to ~50 GB per month. I don't really care about bursts very much.
< GitHub190> [bitcoin] sdaftuar reopened pull request #7222: [WIP] RPC: Indicate which transactions are signaling opt-in RBF (master...add-optin-info) https://github.com/bitcoin/bitcoin/pull/7222
< Luke-Jr> can we get *explicit* ACKs on #7300? otherwise someone has to go make sure the authors actually contributed the code themselves :/
< MarcoFalke> Luke-Jr, only sipa is missing
< MarcoFalke> need to ping when back online
< Luke-Jr> MarcoFalke: lots of people just posted stupid "ACK everything I contribute" which doesn't really help
< Luke-Jr> because git doesn't track who contributed things, only who wrote them
< MarcoFalke> They are legally responsible if they commit copyfraud, how is this our problem? Or asking the other way: How would it help us to get "explicit ACKs" in case a copyfraud is detected and legally pursued?
< GitHub58> [bitcoin] MarcoFalke opened pull request #7374: [init] Rework transaction fee warnings (master...Mf1601-init-fee-warn) https://github.com/bitcoin/bitcoin/pull/7374
< Luke-Jr> MarcoFalke: it's not copyfraud necessarily
< Luke-Jr> MarcoFalke: what if I PR some code from your repo, for example?
< Luke-Jr> MarcoFalke: you didn't contribute it, but you wrote it and git attributes it to you
< GitHub73> [bitcoin] toby opened pull request #7376: Payments: Allow zero value OP_RETURN in PaymentRequests (master...zeropayments) https://github.com/bitcoin/bitcoin/pull/7376
< michagogo> wumpus: btw, I can confirm that adding python to the os x descriptor fixes it
< lpersona> quick question for devs as I was reviewing the 0.12 RC: has the combination of auto setting the min relay fee and RBF enabled a possible attack vector?
< lpersona> I've posted the concern here and want to see if this possibility was considered before doing further research: https://www.reddit.com/r/Bitcoin/comments/41kaxq/autosetting_min_relay_fee_rbf_possible_attack/
< Luke-Jr> lpersona: replied there