--- Day changed Tue Apr 26 2016
00:00 < sipa> cfields: how does this change make travis unusually slow?
00:00 < sipa> cfields: before it is merged
00:01 < sipa> ?
00:01 < sipa> some cache interaction between old and new PRs?
00:02 < cfields> sipa: our special cache flag has been removed, so I'm afraid of that interaction, yes
00:03 < cfields> sipa: in theory it's supposed to work, but i get the impression this path hasn't been tested on their end
00:03 < sipa> ah, i see
00:03 < cfields> sipa: I'll bump a PR real quick to test
00:17 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-core-dev
00:20 -!- jtimon [~quassel@79.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev
00:20 -!- xiangfu [~xiangfu@124.205.70.162] has quit [Ping timeout: 268 seconds]
00:47 < GitHub178> [bitcoin] randy-waterhouse opened pull request #7944: Re-instate TARGET_OS=linux in configure.ac. Removed by 351abf9e035. (master...master) https://github.com/bitcoin/bitcoin/pull/7944
00:47 -!- randy-waterhouse [~kiwigb@opentransactions/dev/randy-waterhouse] has joined #bitcoin-core-dev
00:48 < randy-waterhouse> wumpus: cfields : https://github.com/bitcoin/bitcoin/pull/7944 
00:49 < randy-waterhouse> without this gives a weird runttime qt error (core dump) not linking to xcb plugin correctly (depends build)
01:03 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev
01:03 -!- MarcoFalke [8af6020a@gateway/web/cgi-irc/kiwiirc.com/ip.138.246.2.10] has joined #bitcoin-core-dev
01:09 -!- AaronvanW [~ewout@172pc231.sshunet.nl] has joined #bitcoin-core-dev
01:09 -!- AaronvanW [~ewout@172pc231.sshunet.nl] has quit [Changing host]
01:09 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
01:27 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Ping timeout: 246 seconds]
01:34 -!- jannes [~jannes@178.132.211.90] has joined #bitcoin-core-dev
01:44 -!- supasonic [~supasonic@172-11-188-117.lightspeed.rcsntx.sbcglobal.net] has quit [Ping timeout: 252 seconds]
01:51 -!- paveljanik [~paveljani@94.112.242.230.static.b2b.upcbusiness.cz] has joined #bitcoin-core-dev
01:51 -!- paveljanik [~paveljani@94.112.242.230.static.b2b.upcbusiness.cz] has quit [Changing host]
01:51 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has joined #bitcoin-core-dev
01:52 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Client Quit]
01:56 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has joined #bitcoin-core-dev
01:56 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has quit [Remote host closed the connection]
01:57 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has joined #bitcoin-core-dev
02:07 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Ping timeout: 276 seconds]
02:18 -!- arowser [~quassel@106.120.101.38] has quit [Quit: No Ping reply in 180 seconds.]
02:19 -!- arowser [~quassel@106.120.101.38] has joined #bitcoin-core-dev
02:39 -!- teward [teward@ubuntu/member/teward] has quit [Ping timeout: 250 seconds]
02:58 -!- fanquake [~Adium@unaffiliated/fanquake] has joined #bitcoin-core-dev
03:03 < jonasschnelli> the signal UpdatedBlockTip() is called without holding cs_main, SyncWithWallets() is called while holding cs_main
03:03 < jonasschnelli> I guess the signal listeners do also hold cs_main during the signal callback function?
03:04 < sipa> i think no callbacks should happen while holding a lock
03:04 < jonasschnelli> Yes. Agree. But ConnectTip is under cs_main, right?
03:05 < jonasschnelli> sipa: and connectTip calls SyncWithWallets()
03:05 < sipa> yes, should; not saying they are :)
03:06 < jonasschnelli> I guess a dirty RAII breaking LEAVE_CRITICAL_SECTION() is not the way to go...
03:18 -!- teward [teward@ubuntu/member/teward] has joined #bitcoin-core-dev
03:25 -!- cjcj [2e3b026a@gateway/web/freenode/ip.46.59.2.106] has quit [Quit: Page closed]
03:28 -!- cjcj [2e3b026a@gateway/web/freenode/ip.46.59.2.106] has joined #bitcoin-core-dev
03:29 -!- teward [teward@ubuntu/member/teward] has quit [Ping timeout: 250 seconds]
03:35 < luke-jr> guess we better use Q_EMIT
03:35  * luke-jr hides
03:36 < sipa> how about using dbus?
03:37 < luke-jr> that actually would make sense to add, even if not for internal use :x
03:38 -!- teward [teward@ubuntu/member/teward] has joined #bitcoin-core-dev
03:46 -!- pmienk [~pmienk@c-71-227-177-179.hsd1.wa.comcast.net] has quit [Ping timeout: 252 seconds]
03:54 -!- teward [teward@ubuntu/member/teward] has quit [Ping timeout: 260 seconds]
03:55 < wumpus> what about kdbus, obviously we should aim to bring it all into the kernel
03:59 < wumpus> btw, Q_EMIT works the same as boost signals if it's used within one thread, the event handler is called synchronously. It becomes more interesting if you use it between thread, or somehow with Qt::QueuedConnection, then it will be called later in that event loop
03:59 < sipa> wumpus: i tried uses the ShowProgress signal for better reindex information, but it seems that using that while the main window is up makes it irresponsive (and a non-colored small window shows up)
04:00 < wumpus> sipa: the problem is that something in the GUI may try to get a cs_main lock in response to the signal
04:00 < sipa> so i guess the reindex progress should be reported by extendid UodateTi
04:00 < wumpus> e.g. inthe GUI thrad
04:00 < wumpus> if your code is hogging that signal, it will only proceed after releasing the lock
04:00 < wumpus> hogging that lock, I mean
04:00 < sipa> why does ShowProgress need a lock?
04:00 < wumpus> I don't know
04:00 < wumpus> it may not actually need it, maybe it's a mistake
04:01 < wumpus> ideally the GUI thread would never aquire cs_main at all, unfortunately we're not there yet
04:01 < sipa> it's only used for the startup check now, i think
04:01 < sipa> maybe it's just not or badly implemented for the main window
04:01 < wumpus> but sometimes the GUI wants to fetch some additional statistics from the core, which are not passed in the signal parameters, which require the lock
04:02 < sipa> right
04:02 < wumpus> I don't know for sure but it is usually the explanation for 'GUI stuck' issues
04:02 < wumpus> some of the additional statistics fetches are actually under try_locks to avoid this
04:02 < wumpus> but sometimes there's something sneaky that aquires a cs_main lock deep in the code
04:03 < jonasschnelli> I'm now removing the cs_main lock from the SyncWithWallets signal
04:03 < wumpus> in any case I could take a look at it later
04:03 < wumpus> just push the code somewhere and tell me how to reproduce it
04:03 < jonasschnelli> And I agree with wumpus: we should not allows cs_main locks from the GUI logic itself.
04:03 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has quit [Remote host closed the connection]
04:03 < jonasschnelli> Though, the GUI can call something from the core classes that acquires cs_main
04:04 < wumpus> jonasschnelli: that should be the eventual goal; it's pretty hard to do at the moment though, e.g. sending coins and such should happen in an auxiliary thread
04:04 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has joined #bitcoin-core-dev
04:04 < wumpus> getting data from the core should also happen in an auxiliary thread, and be passed using signals
04:04 < jonasschnelli> Right. We already have something that could work: RPC. :)
04:04 < wumpus> it's not rocket science but not trivial to get entirely right
04:04 < wumpus> yes, you need exactly the same changes if the core were to be remotely
04:05 < wumpus> that's a bonus.
04:05 < jonasschnelli> I think the only change that is worth is to fully process separete the GUI.
04:05 < jonasschnelli> First It could be only the node-GUI (non wallet)
04:05 < wumpus> well it would be a step there
04:05 < wumpus> if all communication to the core hapepns through signals, detaching it is almost trivial
04:05 < jonasschnelli> Right. You need similar/same changes.
04:06 < wumpus> in any case it's been on my todo list for years
04:06 < wumpus> I could focus on it again, but playing around with databases is so much more fun :p
04:08 < wumpus> and for years I believed the GUI would eventually be removed anyway, so didn't feel like spending effort on it
04:08 < wumpus> but you changed things around jonasschnelli :)
04:08 < sipa> i'm sure bitcoin 0.13 will ship with the ability to maintain the utxo set in RAM, in LevelDB, in LMDB, in BDB and in CSV files.
04:09 < wumpus> hahahahah you're on the right track sipa
04:09 < jonasschnelli> hehe...
04:09 < sipa> wumpus: interesting... the Qt GUI was what brought you into bitcoin development in the first place, no?
04:09 < wumpus> sipa: yes, it was
04:10 < sipa> pedrobranco: hi there
04:10 < pedrobranco> hi sipa :)
04:10 < wumpus> I was really optimistic about it in the beginning, but it turned out to be more than I bargained for, I chose qt (with a standard approach) because it is a well-known toolkit in the hope it would attract more developers to it
04:10 < jonasschnelli> I think the Qt GUI is great! Sure, we could use some UX designers. But one step after the other..
04:11 < wumpus> ... but that didn't really happen, and myself I was countinously distracted by other changes that had to be done
04:12 < wumpus> so at some point with all the complaints about the GUI, and with most developers not interested in it anyway, I didn't give it much time before someone would decide to remove it completely
04:12 < pedrobranco> sipa: whats up?
04:12 < sipa> pedrobranco: sorry for all the noise on your importmulti call... i really think we should have such a call
04:13 < MarcoFalke> Interesting, we didn't yet switch to trusty or py3, yet https://github.com/bitcoin/bitcoin/pull/7944 fails due to https://github.com/bitcoin/bitcoin/issues/7893 ...
04:14 < pedrobranco> sipa: no need to sorry, i thank you for the feedback. yes, i think we should too. 
04:14 < wumpus> but anyhow, things changed, also with many of the other desktop wallets effectively dead in the water
04:15 < wumpus> MarcoFalke: maybe someone at Travis pushed The Button
04:15 < sipa> wumpus: yes, the new cache flag was enabled for our repo
04:15 < sipa> we can merge #7920
04:16 < MarcoFalke> Agree, right now things seem to be broken without it.
04:16 < pedrobranco> sipa: your proposal is more accurate on the expected result. looks good to me.
04:18 -!- teward [teward@ubuntu/member/teward] has joined #bitcoin-core-dev
04:19 < jonasschnelli> +1 for 7920
04:20 < GitHub154> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/46880ed2fd96...a4078071e0b4
04:20 < GitHub154> bitcoin/master 89c844d randy-waterhouse: Re-instate TARGET_OS=linux in configure.ac. Removed by 351abf9e035.
04:20 < GitHub154> bitcoin/master a407807 Wladimir J. van der Laan: Merge #7944: Re-instate TARGET_OS=linux in configure.ac. Removed by 351abf9e035....
04:20 < GitHub26> [bitcoin] laanwj closed pull request #7944: Re-instate TARGET_OS=linux in configure.ac. Removed by 351abf9e035. (master...master) https://github.com/bitcoin/bitcoin/pull/7944
04:20 < GitHub111> [bitcoin] laanwj pushed 7 new commits to master: https://github.com/bitcoin/bitcoin/compare/a4078071e0b4...c3e3cfb5d1ea
04:20 < GitHub111> bitcoin/master a6666b2 Wladimir J. van der Laan: depends: mac deploy Py3 compatibility...
04:20 < GitHub111> bitcoin/master 06fdffd Cory Fields: travis: switch to Trusty
04:20 < GitHub111> bitcoin/master 9267a47 Cory Fields: depends: enable pre-compiled headers for qt...
04:21 < GitHub8> [bitcoin] laanwj closed pull request #7920: Switch Travis to Trusty (master...travis-trusty) https://github.com/bitcoin/bitcoin/pull/7920
04:22 < GitHub0> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/c3e3cfb5d1ea...0ea394188611
04:22 < GitHub0> bitcoin/master 62a9abd Chris Stewart: Fixing comment in script_test.json test case
04:22 < GitHub0> bitcoin/master 0ea3941 Wladimir J. van der Laan: Merge #7941: Fixing comment in script_test.json test case...
04:22 < GitHub188> [bitcoin] laanwj closed pull request #7941: Fixing comment in script_test.json test case (master...fix_script_test_comment) https://github.com/bitcoin/bitcoin/pull/7941
04:23 < sipa> do we backport it to 0.12? PRs against 0.12 may be very slow otherwise
04:23 < GitHub135> [bitcoin] laanwj pushed 6 new commits to master: https://github.com/bitcoin/bitcoin/compare/0ea394188611...e26b62093ae2
04:23 < GitHub135> bitcoin/master f8e6fb1 Pieter Wuille: Introduce constant for maximum CScript length
04:23 < GitHub135> bitcoin/master 4f87af6 Pieter Wuille: Treat overly long scriptPubKeys as unspendable
04:23 < GitHub135> bitcoin/master 4bf631e Patrick Strateman: CDataStream::ignore Throw exception instead of assert on negative nSize....
04:24 < GitHub86> [bitcoin] laanwj closed pull request #7933: Fix OOM when deserializing UTXO entries with invalid length (master...fixcompressoroom) https://github.com/bitcoin/bitcoin/pull/7933
04:24 -!- teward [teward@ubuntu/member/teward] has quit [Ping timeout: 276 seconds]
04:24 < MarcoFalke> sipa, looks like we have to
04:26 < GitHub38> [bitcoin] laanwj closed pull request #7936: CDataStream::ignore Throw exception instead of assert on negative nSize. (master...2016-04-24-cdatastream-ignore) https://github.com/bitcoin/bitcoin/pull/7936
04:26 < btcdrak> so does this mean we can merge #7165?
04:27 < GitHub157> [bitcoin] MarcoFalke opened pull request #7945: Revert "travis: temporarily disable qt to avoid timeouts" (master...Mf1604-travisQtCache) https://github.com/bitcoin/bitcoin/pull/7945
04:27 < wumpus> let's first see if the travis passes btcdrak
04:32 < wumpus> sipa: yes, I think the test changes should be backported to 0.12
04:32 < wumpus> but let's make sure it's stable on master first
04:32 < wumpus> then do that in one go
04:33 < sipa> agree
04:33 < sipa> no hurry for the backports
04:36 -!- cryptapus_ [~cyptapus@87.254.202.228] has joined #bitcoin-core-dev
04:36 -!- cryptapus_ [~cyptapus@87.254.202.228] has quit [Changing host]
04:36 -!- cryptapus_ [~cyptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev
04:49 -!- cryptapus_ is now known as cryptapus
04:57 -!- BCBot [~BCBot@55.107.196.104.bc.googleusercontent.com] has quit [Ping timeout: 240 seconds]
05:03 < GitHub138> [bitcoin] jonasschnelli opened pull request #7946: Reduce cs_main locks during ConnectTip/SyncWithWallets (master...2016/04/cs_main_wallet) https://github.com/bitcoin/bitcoin/pull/7946
05:14 < jonasschnelli> Okay. Am besten nimmst Du dann auch noch Taxi/Zug/Essen kosten obendrauf.
05:14 < jonasschnelli> arg.. wrong window. Sry.
05:14 < GitHub95> [bitcoin] hmel opened pull request #7947: Global params cleanup (master...global-params-cleanup) https://github.com/bitcoin/bitcoin/pull/7947
05:19 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
05:21 -!- randy-waterhouse [~kiwigb@opentransactions/dev/randy-waterhouse] has quit [Quit: Leaving.]
05:27 -!- NotAnNSAgent [~NotAnNSAg@46.166.190.174] has joined #bitcoin-core-dev
05:28 < jonasschnelli> sipa: during ActivateBestChainStep, connectTip can only be get  the pblock pointer (CBlock* pblock from ActivateBestChainStep()) or NULL? Right?
05:29 < jonasschnelli> So we can only sync the transactions from the block passed into ActivateBestChainStep()?
05:29 < sipa> heh, no
05:29 -!- teward [teward@ubuntu/member/teward] has joined #bitcoin-core-dev
05:30 < sipa> activatebestchainstep can activate or deactivate multiple blocks
05:30 < sipa> that pblock is just an optimization
05:30 < jonasschnelli> Right!
05:30 < jonasschnelli> There is a ReadBlockFromDisk...
05:30 < jonasschnelli> okay... will fix it.
05:30 < sipa> so it doesn't need to load that specific block again from disk if we already habe it
05:32 < jonasschnelli> Right. I think I form a std::list with all relevant transactions... should not exhaust the memory I guess.
05:36 < sipa> a vector will be more efficient
05:39 < jonasschnelli> sipa: because it doesn't need to check for duplicates?
05:40 < jonasschnelli> s/for duplicates/if item already exists
05:40 < sipa> because it doesn't need to allocate a new memory block for each item
05:42 -!- teward [teward@ubuntu/member/teward] has quit [Ping timeout: 276 seconds]
05:47 < jonasschnelli> Arg.. why does the SyncWithWallet signal requires a "const CBlock* pblock"!
05:48 < sipa> to know which block it came from :)
05:49 < jonasschnelli> sipa: But the hash should enough?!
05:49 < sipa> since we removed the merkle branches, i think that's correct
05:50 < jonasschnelli> the only problematic part would be: https://github.com/bitcoin/bitcoin/blob/master/src/wallet/wallet.cpp#L3288
05:50 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev
05:51 < sipa> that's just a sanity check, i think
05:51 < sipa> oh, no, it is not
05:51 < sipa> we could change the signal to pass a CBlockIndex* and the position in the vtx vector
05:51 < jonasschnelli> Right!
05:52 < jonasschnelli> I try that.
05:55 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Client Quit]
05:58 -!- sdaftuar [~sdaftuar@unaffiliated/sdaftuar] has quit [Ping timeout: 244 seconds]
05:58 -!- morcos [~morcos@static-100-38-11-146.nycmny.fios.verizon.net] has quit [Ping timeout: 244 seconds]
05:59 -!- zxzzt [~prod@static-100-38-11-146.nycmny.fios.verizon.net] has quit [Ping timeout: 244 seconds]
05:59 -!- sdaftuar [~sdaftuar@unaffiliated/sdaftuar] has joined #bitcoin-core-dev
05:59 < jonasschnelli> sipa: I think the wallet does not need to know at which position the transaction is in the block. Only if it in a block or not.
05:59 < jonasschnelli> I don't see a usage of nIndex
05:59 -!- morcos [~morcos@rrcs-67-251-193-154.nyc.biz.rr.com] has joined #bitcoin-core-dev
06:00 -!- zxzzt [~prod@rrcs-67-251-193-154.nyc.biz.rr.com] has joined #bitcoin-core-dev
06:00 < jonasschnelli> well,... there is one.
06:01  * jonasschnelli hates when touching a single thing results in touching the whole codebase.
06:07 < sipa> jonasschnelli: we use nIndex==-1 to indicate "conflicted"
06:07 < sipa> also, it may be useful in the future
06:11 < jonasschnelli> sipa: Yes. And we use the position for "merges" https://github.com/bitcoin/bitcoin/blob/master/src/wallet/wallet.cpp#L715
06:42 -!- TomMc [~tom@unaffiliated/tommc] has joined #bitcoin-core-dev
06:43 < jonasschnelli> I think this should work now as intended: https://github.com/bitcoin/bitcoin/pull/7946/files
06:43 < jonasschnelli> Lets see what travis thinks about it.
06:44 -!- teward [teward@ubuntu/member/teward] has joined #bitcoin-core-dev
06:44 -!- zooko [~user@c-73-217-16-2.hsd1.co.comcast.net] has joined #bitcoin-core-dev
06:54 -!- Samdney [~Samdney@dyn-ant666999.hawo.ipv6.uni-erlangen.de] has joined #bitcoin-core-dev
07:05 -!- fanquake1 [~Adium@125.253.101.232] has joined #bitcoin-core-dev
07:06 -!- fanquake1 [~Adium@125.253.101.232] has quit [Remote host closed the connection]
07:06 -!- fanquake1 [~Adium@125.253.101.232] has joined #bitcoin-core-dev
07:07 -!- fanquake [~Adium@unaffiliated/fanquake] has quit [Ping timeout: 260 seconds]
07:10 -!- supasonic [~supasonic@172-11-188-117.lightspeed.rcsntx.sbcglobal.net] has joined #bitcoin-core-dev
07:15 -!- bsm117532 [~mcelrath@38.121.165.30] has quit [Remote host closed the connection]
07:29 -!- cjcj [2e3b026a@gateway/web/freenode/ip.46.59.2.106] has quit [Quit: Page closed]
07:41 < GitHub176> [bitcoin] mruddy opened pull request #7948: RPC: add locked_in block hash to getblockchaininfo bip9_softforks data (master...version_bits_locked_in_block) https://github.com/bitcoin/bitcoin/pull/7948
07:58 < sipa> [A
07:58 < sipa> [A
07:58 < helo> :D
08:09 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection]
08:19 -!- earlest [~denetrabu@96.93.57.150] has joined #bitcoin-core-dev
08:20 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev
08:22 -!- bysherper [~denetrabu@96.93.57.150] has quit [Ping timeout: 240 seconds]
08:26 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt]
08:29 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev
08:33 < GitHub26> [bitcoin] jonasschnelli opened pull request #7949: [RPC] Add RPC long poll notifications (master...2016/04/rpc_signals) https://github.com/bitcoin/bitcoin/pull/7949
08:42 -!- baldur [~baldur@pool-108-29-176-11.nycmny.fios.verizon.net] has quit [Ping timeout: 260 seconds]
08:44 -!- zooko [~user@c-73-217-16-2.hsd1.co.comcast.net] has quit [Ping timeout: 244 seconds]
08:47 -!- cryptocoder [~cryptocod@cpe-76-90-140-31.socal.res.rr.com] has quit [Quit: cryptocoder]
08:56 < btcdrak> looks like that Travis merge went ok
09:00 < cfields> btcdrak: yea, but there's a big backlog atm :(
09:01 < btcdrak> cfields: 15 PRs, heh. Do they all need to rebase to take advantage as well?
09:01 -!- fanquake1 [~Adium@125.253.101.232] has quit [Quit: Leaving.]
09:02 -!- zooko [~user@2601:281:8000:8387:ad7b:7186:52c2:5708] has joined #bitcoin-core-dev
09:02 < cfields> btcdrak: no, cache is built now. But anything going into 0.12 will take forever until the travis change is backported.
09:03 < cfields> I didn't think that would be an immediate issue.. should've PR'd them in parallel
09:03 -!- Guest4820 [~chatzilla@97-90-24-187.dhcp.mtpk.ca.charter.com] has joined #bitcoin-core-dev
09:04 < btcdrak> cfields: exciting :) nicely done!
09:04 -!- Guest4820 is now known as roidster
09:05 < cfields> btcdrak: thanks. Now to work on speeding things up
09:06 < cfields> MarcoFalke: wasn't there some discussion a while back about running the rpc tests in parallel?
09:09 < cfields> jonasschnelli: I was wishing for a polling interface recently as well. I'd be curious to know how much it could speed up rpc tests
09:10 < jonasschnelli> cfields: hm... haven't though about that. But right, this might be capable of speeding up the tests
09:10 < jonasschnelli> adding now multiple listeners support
09:11 < cfields> jonasschnelli: all of the tests that constantly ping for blockcount, received tx, etc. There are lots of while(1){wait(0.1)}'s around, iirc
09:11 < jonasschnelli> cfields: Yes. Would be interesting to see if these could be avoided with the RPC signals pull.
09:12 < GitHub57> [bitcoin] MarcoFalke opened pull request #7950: [0.12] travis: switch to Trusty (0.12...Mf1604-012travisTrusty) https://github.com/bitcoin/bitcoin/pull/7950
09:14 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has joined #bitcoin-core-dev
09:16 < GitHub25> [bitcoin] MarcoFalke opened pull request #7951: [qa] test_framework: Properly print exception (master...Mf1604-qaMinorFixes) https://github.com/bitcoin/bitcoin/pull/7951
09:16 -!- cryptocoder [~cryptocod@cpe-76-90-140-31.socal.res.rr.com] has joined #bitcoin-core-dev
09:17 -!- PRab [~chatzilla@c-68-34-102-231.hsd1.mi.comcast.net] has quit [Ping timeout: 252 seconds]
09:21 -!- abritoid [~abritoid@46.16.193.99] has quit [Quit: O.o]
09:21 -!- shesek [~shesek@bzq-84-110-109-203.red.bezeqint.net] has joined #bitcoin-core-dev
09:31 -!- Don_John [~Don@249-223-114-134.nat.resnet.nau.edu] has joined #bitcoin-core-dev
09:31 -!- Don_John [~Don@249-223-114-134.nat.resnet.nau.edu] has quit [Remote host closed the connection]
09:32 -!- cryptocoder [~cryptocod@cpe-76-90-140-31.socal.res.rr.com] has quit [Quit: cryptocoder]
09:34 -!- pmienk [~pmienk@c-71-227-177-179.hsd1.wa.comcast.net] has joined #bitcoin-core-dev
09:50 -!- arowser [~quassel@106.120.101.38] has quit [Quit: No Ping reply in 180 seconds.]
09:50 -!- arowser [~quassel@106.120.101.38] has joined #bitcoin-core-dev
09:51 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has quit [Remote host closed the connection]
09:55 -!- bysherper [~denetrabu@96.93.57.150] has joined #bitcoin-core-dev
09:58 -!- earlest [~denetrabu@96.93.57.150] has quit [Ping timeout: 240 seconds]
10:00 -!- achow101 [~achow101@pool-96-227-114-115.phlapa.fios.verizon.net] has joined #bitcoin-core-dev
10:02 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has joined #bitcoin-core-dev
10:17 -!- Eliel_ [~jojkaart@91.154.164.164] has quit [Ping timeout: 250 seconds]
10:29 -!- Eliel [~jojkaart@a91-154-164-164.elisa-laajakaista.fi] has joined #bitcoin-core-dev
10:42 -!- murch [~murch@p4FE39266.dip0.t-ipconnect.de] has quit [Remote host closed the connection]
10:50 -!- wangchun [~wangchun@li414-193.members.linode.com] has quit [Quit: leaving]
10:51 -!- wangchun [~wangchun@li414-193.members.linode.com] has joined #bitcoin-core-dev
11:17 -!- JackH [~Jack@79-73-185-113.dynamic.dsl.as9105.com] has joined #bitcoin-core-dev
11:21 -!- cryptocoder [~cryptocod@cpe-76-90-140-31.socal.res.rr.com] has joined #bitcoin-core-dev
11:26 -!- earlest [~denetrabu@96.93.57.150] has joined #bitcoin-core-dev
11:29 -!- bysherper [~denetrabu@96.93.57.150] has quit [Ping timeout: 240 seconds]
11:30 -!- [\\\] [~triplesla@unaffiliated/imsaguy] has quit [Ping timeout: 252 seconds]
11:36 -!- belcher [~user@unaffiliated/belcher] has joined #bitcoin-core-dev
11:41 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has quit [Remote host closed the connection]
11:41 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has joined #bitcoin-core-dev
11:41 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has quit [Remote host closed the connection]
11:43 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has quit [Remote host closed the connection]
11:44 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has joined #bitcoin-core-dev
11:47 -!- Giszmo [~leo@pc-122-14-46-190.cm.vtr.net] has joined #bitcoin-core-dev
11:49 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-core-dev
11:49 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has quit [Ping timeout: 250 seconds]
11:55 -!- belcher [~user@unaffiliated/belcher] has quit [Read error: Connection reset by peer]
12:04 -!- belcher [~user@unaffiliated/belcher] has joined #bitcoin-core-dev
12:10 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has joined #bitcoin-core-dev
12:18 -!- pedrobranco [~pedrobran@167.225.61.94.rev.vodafone.pt] has joined #bitcoin-core-dev
12:18 -!- bysherper [~denetrabu@96.93.57.150] has joined #bitcoin-core-dev
12:21 -!- cryptocoder [~cryptocod@cpe-76-90-140-31.socal.res.rr.com] has quit [Quit: cryptocoder]
12:21 -!- earlest [~denetrabu@96.93.57.150] has quit [Ping timeout: 240 seconds]
12:22 -!- pedrobranco [~pedrobran@167.225.61.94.rev.vodafone.pt] has quit [Ping timeout: 252 seconds]
12:25 -!- cryptocoder [~cryptocod@cpe-76-90-140-31.socal.res.rr.com] has joined #bitcoin-core-dev
12:39 -!- pedrobranco [~pedrobran@167.225.61.94.rev.vodafone.pt] has joined #bitcoin-core-dev
12:43 -!- earlest [~denetrabu@96.93.57.150] has joined #bitcoin-core-dev
12:43 -!- pedrobranco [~pedrobran@167.225.61.94.rev.vodafone.pt] has quit [Ping timeout: 250 seconds]
12:46 -!- bysherper [~denetrabu@96.93.57.150] has quit [Ping timeout: 240 seconds]
12:49 -!- NotAnNSAgent [~NotAnNSAg@46.166.190.174] has left #bitcoin-core-dev []
12:53 < paveljanik> anyone having problem on testnet with "block is marked invalid" right now?
12:54 < paveljanik> my node is not able to finish IBD
12:54 < paveljanik> 2016-04-26 19:53:40 received: headers (32808 bytes) peer=1
12:54 < paveljanik> 2016-04-26 19:53:40 ERROR: AcceptBlockHeader: block is marked invalid
12:54 < paveljanik> 2016-04-26 19:53:40 ERROR: invalid header received
12:54 < paveljanik> 2016-04-26 19:53:40 ProcessMessages(headers, 32808 bytes) FAILED peer=1
12:55 -!- cryptapus [~cyptapus@unaffiliated/cryptapus] has quit [Ping timeout: 246 seconds]
12:58 < sdaftuar> paveljanik: IBD takes a while if your initial headers sync is from a bad peer (in this case, a peer that is on a chain you think is invalid)
12:58 < sdaftuar> paveljanik: it should clear up on its own after one of your other peers announces a new block.
12:59 < sdaftuar> (at least, that's my guess)
12:59 < paveljanik> ok, I'll wait a bit.
12:59 < paveljanik> Thanks
13:02 < sdaftuar> paveljanik: hm.  after slightly more investigation, i don't have a good explanation of what you're seeing after all -- looks like the bad peer should have been disconnected, and then you should have requested headers from one of your other peers...
13:02 -!- bysherper [~denetrabu@96.93.57.150] has joined #bitcoin-core-dev
13:04 -!- muuqwaul [~denetrabu@96.93.57.150] has joined #bitcoin-core-dev
13:05 -!- earlest [~denetrabu@96.93.57.150] has quit [Ping timeout: 240 seconds]
13:07 < paveljanik> I did disconnect peers one by one
13:07 < paveljanik> and now the same for other peer
13:07 -!- bysherper [~denetrabu@96.93.57.150] has quit [Ping timeout: 240 seconds]
13:08 < sdaftuar> interesting
13:08 < sdaftuar> looks to me like if you have 2 peers on the same bad chain
13:09 < sdaftuar> and the first one feeds you an invalid header, you'll disconnect from it
13:09 < sdaftuar> but then if the second one feeds the same bad header to you, you'll get exactly the error message you pasted, but no disconnect
13:10 < sdaftuar> that seems unfortunate
13:10 < sdaftuar> what height are you at?
13:11 < paveljanik> 787628
13:11 < paveljanik> I'll print the block hash of the invalid block to the log to see more...
13:12 -!- arowser [~quassel@106.120.101.38] has quit [Quit: No Ping reply in 180 seconds.]
13:12 -!- arowser [~quassel@106.120.101.38] has joined #bitcoin-core-dev
13:12 < paveljanik> I'm at 787628
13:12 < sdaftuar> checking my logs for invalid block headers...
13:12 < paveljanik> and the logged message is: ERROR: AcceptBlockHeader: block 00000000000005354772cb50ea2decd1e9176724c41eb3427197943aea33194e is marked invalid
13:13 < paveljanik> this is 787391
13:13 < paveljanik> 8)
13:13 < sdaftuar> yeah i see a big invalidchainfound message about that
13:17 < sdaftuar> looks like maybe the chain forked after CSV deployed on testnet
13:17 < sdaftuar> ERROR: ConnectBlock: contains a non-BIP68-final transaction
13:18 < sdaftuar> sounds like you need some 0.12.1 peers...
13:19 < paveljanik> 8) OK, I'll disconnect all nodes but 0.12.99
13:21 < paveljanik> looks like everyone moved from testnet to segnets ;-)
13:21 < sdaftuar> heh maybe!
13:26 < GitHub9> [bitcoin] paveljanik opened pull request #7952: Log invalid block hash to make debugging easier. (master...20160426_Log_invalid_block) https://github.com/bitcoin/bitcoin/pull/7952
13:38 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has joined #bitcoin-core-dev
13:38 -!- pmienk [~pmienk@c-71-227-177-179.hsd1.wa.comcast.net] has quit [Ping timeout: 244 seconds]
13:42 -!- cryptapus_afk is now known as cryptapus
13:54 -!- pmienk [~pmienk@c-71-227-177-179.hsd1.wa.comcast.net] has joined #bitcoin-core-dev
14:16 -!- JackH [~Jack@79-73-185-113.dynamic.dsl.as9105.com] has quit [Remote host closed the connection]
14:22 -!- droark [~droark@c-24-22-36-12.hsd1.or.comcast.net] has joined #bitcoin-core-dev
14:23 < Chris_Stewart_5> Shouldn't this be a INVALID_STACK_OPERATION instead of a BAD_OPCODE?
14:23 < Chris_Stewart_5> https://github.com/bitcoin/bitcoin/blob/master/src/test/data/script_tests.json#L719
14:24 -!- JackH [~Jack@79-73-185-113.dynamic.dsl.as9105.com] has joined #bitcoin-core-dev
14:26 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Read error: Connection reset by peer]
14:27 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has joined #bitcoin-core-dev
14:27 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Remote host closed the connection]
14:29 -!- tripleslash is now known as imsaguy
14:32 -!- imsaguy is now known as tripleslash
14:39 -!- neha [~narula@mint-square.mit.edu] has quit [Ping timeout: 260 seconds]
14:39 -!- neha [~narula@mint-square.mit.edu] has joined #bitcoin-core-dev
14:46 -!- JackH [~Jack@79-73-185-113.dynamic.dsl.as9105.com] has quit [Remote host closed the connection]
14:51 -!- jannes [~jannes@178.132.211.90] has quit [Quit: Leaving]
14:53 -!- JackH [~Jack@79-73-185-113.dynamic.dsl.as9105.com] has joined #bitcoin-core-dev
15:19 -!- cryptapus is now known as cryptapus_afk
15:20 < Chris_Stewart_5> also, are there not any CHECKSEQUENCEVERIFY tests inside of script_tests?
15:24 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)]
15:35 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has quit [Remote host closed the connection]
15:47 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 252 seconds]
15:48 -!- tripleslash is now known as imsaguy
15:50 -!- gevs [~greg@unaffiliated/gevs] has quit [Ping timeout: 244 seconds]
15:50 -!- heath is now known as ybit
16:02 -!- gevs [~greg@ip-83-134-234-91.dsl.scarlet.be] has joined #bitcoin-core-dev
16:02 -!- gevs [~greg@ip-83-134-234-91.dsl.scarlet.be] has quit [Changing host]
16:02 -!- gevs [~greg@unaffiliated/gevs] has joined #bitcoin-core-dev
16:04 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has quit [Read error: Connection reset by peer]
16:10 -!- TomMc [~tom@unaffiliated/tommc] has quit [Ping timeout: 250 seconds]
16:19 -!- Guest48555 is now known as petertodd
16:36 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has joined #bitcoin-core-dev
16:38 -!- cryptocoder [~cryptocod@cpe-76-90-140-31.socal.res.rr.com] has quit [Quit: cryptocoder]
16:41 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has quit [Ping timeout: 250 seconds]
16:41 -!- assder [82ebca3a@gateway/web/freenode/ip.130.235.202.58] has quit [Ping timeout: 250 seconds]
16:45 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has joined #bitcoin-core-dev
16:50 -!- supasonic [~supasonic@172-11-188-117.lightspeed.rcsntx.sbcglobal.net] has quit [Ping timeout: 276 seconds]
16:52 -!- supasonic [~supasonic@172-11-188-117.lightspeed.rcsntx.sbcglobal.net] has joined #bitcoin-core-dev
16:52 -!- jonasschnelli [~jonasschn@unaffiliated/jonasschnelli] has quit [Ping timeout: 250 seconds]
17:00 -!- jonasschnelli [~jonasschn@2a01:4f8:200:7025::2] has joined #bitcoin-core-dev
17:03 -!- PRab [~chatzilla@c-68-34-102-231.hsd1.mi.comcast.net] has joined #bitcoin-core-dev
17:06 -!- supasonic [~supasonic@172-11-188-117.lightspeed.rcsntx.sbcglobal.net] has quit [Ping timeout: 260 seconds]
17:14 -!- belcher [~user@unaffiliated/belcher] has quit [Quit: Leaving]
17:19 -!- BonyM [~BonyM-I@ua-83-227-211-4.cust.bredbandsbolaget.se] has joined #bitcoin-core-dev
17:19 -!- supasonic [~supasonic@172-11-188-117.lightspeed.rcsntx.sbcglobal.net] has joined #bitcoin-core-dev
17:22 -!- BonyM1 [~BonyM-I@ua-83-227-211-4.cust.bredbandsbolaget.se] has joined #bitcoin-core-dev
17:22 -!- BonyM [~BonyM-I@ua-83-227-211-4.cust.bredbandsbolaget.se] has quit [Read error: Connection reset by peer]
17:22 -!- BonyM1 [~BonyM-I@ua-83-227-211-4.cust.bredbandsbolaget.se] has quit [Write error: Connection reset by peer]
17:22 -!- BonyM [~BonyM-I@ua-83-227-211-4.cust.bredbandsbolaget.se] has joined #bitcoin-core-dev
17:23 -!- BonyM [~BonyM-I@ua-83-227-211-4.cust.bredbandsbolaget.se] has quit [Read error: Connection reset by peer]
17:23 -!- BonyM [~BonyM-I@ua-83-227-211-4.cust.bredbandsbolaget.se] has joined #bitcoin-core-dev
17:26 -!- Samdney [~Samdney@dyn-ant666999.hawo.ipv6.uni-erlangen.de] has quit [Ping timeout: 268 seconds]
17:31 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-otfvkmwvititjjxc] has quit [Quit: Connection closed for inactivity]
17:39 < achow101> The current master fails to cross compile for windows for me. Anyone else see this?
17:48 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
17:56 -!- BonyM [~BonyM-I@ua-83-227-211-4.cust.bredbandsbolaget.se] has quit [Quit: Leaving]
18:12 -!- NotAnNSAgent [~NotAnNSAg@46.166.190.158] has joined #bitcoin-core-dev
18:20 -!- BonyM [~BonyM-I@ua-83-227-211-4.cust.bredbandsbolaget.se] has joined #bitcoin-core-dev
18:30 -!- dermoth [~thomas@dsl-66-36-157-105.mtl.aei.ca] has quit [Read error: Connection reset by peer]
18:31 -!- dermoth [~thomas@dsl-66-36-157-105.mtl.aei.ca] has joined #bitcoin-core-dev
19:02 -!- BonyM [~BonyM-I@ua-83-227-211-4.cust.bredbandsbolaget.se] has quit [Ping timeout: 260 seconds]
19:08 -!- moli [~molly@unaffiliated/molly] has quit [Read error: Connection reset by peer]
19:09 -!- moli [~molly@unaffiliated/molly] has joined #bitcoin-core-dev
19:10 -!- arowser [~quassel@106.120.101.38] has quit [Quit: No Ping reply in 180 seconds.]
19:11 -!- arowser [~quassel@106.120.101.38] has joined #bitcoin-core-dev
19:19 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Quit: WeeChat 0.4.2]
19:21 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev
19:22 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Client Quit]
19:22 -!- Giszmo [~leo@pc-122-14-46-190.cm.vtr.net] has quit [Quit: Leaving.]
19:28 -!- Cory [~C@unaffiliated/cory] has quit [Ping timeout: 250 seconds]
19:30 -!- Pasha [~C@unaffiliated/cory] has joined #bitcoin-core-dev
19:34 < GitHub193> [bitcoin] achow101 opened pull request #7953: Create signmessagewithprivkey rpc (master...signmessagewithprivkey) https://github.com/bitcoin/bitcoin/pull/7953
19:37 -!- Pasha is now known as Cory
19:51 -!- zooko [~user@2601:281:8000:8387:ad7b:7186:52c2:5708] has quit [Ping timeout: 276 seconds]
19:51 -!- fkhan [weechat@gateway/vpn/mullvad/x-rhlvsadwfqbvjylk] has quit [Read error: Connection reset by peer]
19:59 -!- fengling [~fengling@111.198.29.53] has joined #bitcoin-core-dev
20:11 -!- TomMc [~tom@unaffiliated/tommc] has joined #bitcoin-core-dev
20:19 -!- TomMc [~tom@unaffiliated/tommc] has quit [Ping timeout: 244 seconds]
20:20 -!- achow101 [~achow101@pool-96-227-114-115.phlapa.fios.verizon.net] has quit [Read error: Connection reset by peer]
20:20 -!- fkhan [weechat@gateway/vpn/mullvad/x-ossilvhqbkqrliby] has joined #bitcoin-core-dev
20:24 -!- pmienk [~pmienk@c-71-227-177-179.hsd1.wa.comcast.net] has quit [Ping timeout: 240 seconds]
20:37 -!- pmienk [~pmienk@c-71-227-177-179.hsd1.wa.comcast.net] has joined #bitcoin-core-dev
20:39 -!- cryptapus_afk [~cryptapus@unaffiliated/cryptapus] has quit [Ping timeout: 268 seconds]
20:47 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
20:48 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev
21:03 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
21:04 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev
21:29 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
21:30 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev
21:35 -!- zooko [~user@2601:281:8000:8387:acfd:928a:debb:8587] has joined #bitcoin-core-dev
21:53 -!- NotAnNSAgent [~NotAnNSAg@46.166.190.158] has quit [Quit: NotAnNSAgent]
22:02 -!- pedrobranco [~pedrobran@167.225.61.94.rev.vodafone.pt] has joined #bitcoin-core-dev
22:07 -!- pedrobranco [~pedrobran@167.225.61.94.rev.vodafone.pt] has quit [Ping timeout: 260 seconds]
22:19 < GitHub115> [bitcoin] theuni opened pull request #7954: build: quiet annoying warnings without adding new ones (master...clean-warnings) https://github.com/bitcoin/bitcoin/pull/7954
22:24 < GitHub131> [bitcoin] pstratem opened pull request #7955: [WIP] sync mempool after new block (master...2016-04-26-mempoolsync) https://github.com/bitcoin/bitcoin/pull/7955
22:30 -!- xiangfu [~xiangfu@111.198.29.53] has joined #bitcoin-core-dev
22:35 -!- xiangfu [~xiangfu@111.198.29.53] has quit [Ping timeout: 260 seconds]
22:36 -!- fengling [~fengling@111.198.29.53] has quit [Ping timeout: 240 seconds]
22:36 -!- xiangfu [~xiangfu@111.198.29.53] has joined #bitcoin-core-dev
22:42 -!- supasonic [~supasonic@172-11-188-117.lightspeed.rcsntx.sbcglobal.net] has quit [Ping timeout: 244 seconds]
22:42 -!- supasonic [~supasonic@172-11-188-117.lightspeed.rcsntx.sbcglobal.net] has joined #bitcoin-core-dev
22:53 -!- roidster [~chatzilla@97-90-24-187.dhcp.mtpk.ca.charter.com] has quit [Quit: ChatZilla 0.9.92 [SeaMonkey 2.39/20151103191810]]
23:00 -!- dermoth [~thomas@dsl-66-36-157-105.mtl.aei.ca] has quit [Read error: Connection reset by peer]
23:01 -!- dermoth [~thomas@dsl-66-36-157-105.mtl.aei.ca] has joined #bitcoin-core-dev
23:04 -!- arowser [~quassel@106.120.101.38] has quit [Quit: No Ping reply in 180 seconds.]
23:04 -!- arowser [~quassel@106.120.101.38] has joined #bitcoin-core-dev
23:07 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-core-dev
23:08 -!- fengling [~fengling@111.198.29.53] has joined #bitcoin-core-dev
23:17 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection]
23:20 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Ping timeout: 260 seconds]
23:30 -!- Thireus [~Thireus@vps-92.197.170.217.stwvps.net] has quit [Quit: Leaving.]
23:32 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-qwiludxwapxvpbrm] has joined #bitcoin-core-dev
23:37 < gmaxwell> So -- we have bytessent_per_msg and bytesrecv_per_msg ... would it be insane to ahve a bytes_implied to track bytes of blocks implicitly sent/recieved via comprblock/blocktxn in matt's block relay code?
23:38 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-core-dev
23:41 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev
23:53 < da2ce7_mobile> is there a easy way to 'reset' an unconfirmed transaction in Bitcoin-QT?
23:54 -!- cryptocoder [~cryptocod@149.142.244.168] has joined #bitcoin-core-dev
23:59 -!- binns [sid105317@21/bitcoin/binns] has quit [Ping timeout: 264 seconds]
23:59 -!- Expanse [sid146237@gateway/web/irccloud.com/x-qjpyohkgmbzvgobg] has quit [Ping timeout: 264 seconds]
23:59 -!- ibrightly [sid113387@gateway/web/irccloud.com/x-hnjdxuzikjmkenan] has quit [Ping timeout: 264 seconds]
23:59 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev