< jon_> Having a problem with bitcoin core can anyone help?
< GitHub142> [bitcoin] MarcoFalke opened pull request #7720: [qa] rpc-test: Normalize assert() (master...Mf1603-qaAssertNorm) https://github.com/bitcoin/bitcoin/pull/7720
< Chris_Stewart_5> is there a function in bitcoin core to write a transaction's hex to stdout?
< sipa> CDataStream ss(SER_NETWORK, PROTOCOL_VERSION); ss << transaction; printf("Transaction: %s\n", HexStr(ss).c_str());
< Chris_Stewart_5> any of the three or do those three lines need to be executed in sequence
< Chris_Stewart_5> oh nvm
< sipa> in sequence
< Chris_Stewart_5> Looks like it worked perfectly, thanks sipa that saved me a lot of time
< jonasschnelli> Chris_Stewart_5: Ah. Right. Wasn't looking into this channel.
< Chris_Stewart_5> Yeah I always like to try and ask in #bitcoin-dev before I ask in this channel :/
< jonasschnelli> Right. That's good.
< GitHub127> [bitcoin] MarcoFalke opened pull request #7721: [qa] Use print() in rpc tests (master...Mf1603-qaPy3print) https://github.com/bitcoin/bitcoin/pull/7721
< jonasschnelli> cfields: Whats the reason of setting a first_read_cb while also setting the evbuffer_add_cb (https://github.com/theuni/libbtcnet/blob/64ade4933bc7295fb445f26c998634c50b28b4c0/src/connectionbase.cpp#L167)?
< cfields> jonasschnelli: 2 callbacks are added. one for events, one purely to report read/write chunks
< jonasschnelli> cfields: Okay. But after you get a callback on first_read_cb(), you redirect to read_cb,.. why exactly?
< cfields> jonasschnelli: more specifically, for the bufferevents, watermarks are used so that data reads are only reported for each complete message. for the evbuffers, it'll report every time a chunk is read/written from the socket
< cfields> jonasschnelli: there's a timeout of N seconds before we disconnect from a peer if no data is read/written. After that first read/write, the initial timeout is no longer needed, and we switch to the regular timeout value
< jonasschnelli> cfields: Okay. I see. evbuffer_add_cb(input, read_data, this); adds an additional callback.
< jonasschnelli> And the first_read_cb is for the different timeouts
< cfields> jonasschnelli: sorry, "if no data is *ever read/written"
< jonasschnelli> Okay. Thanks!
< cfields> jonasschnelli: thanks for reviewing! Please fire away with questions. I'd like to document it thoroughly, just not quite sure how
< jonasschnelli> cfields: I'll try now to understand the code,... its a pre-step for the review. :)
< cfields> it's probably worth commenting every time the callbacks are set.
< cfields> adding that to the todo
< madu> hello
< madu> someone there?
< sipa> nope, sorry
< madu> damn
< madu> thats sad
< sipa> :)
< madu> sipa
< madu> do you know how i can change something in the translation ?
< madu> of the gui
< MarcoFalke> translations are done on transifex
< madu> i changed somethings e.g. in bitcoin_de.ts and used lrelease to update bitcoin_de.qm
< madu> but the translations does not change
< MarcoFalke> We only pull them from transifex before every rc:
< madu> i dont understand
< madu> every translation will get updated?
< madu> i just wanna change the translation in my client
< sipa> MarcoFalke: you're not answering madu's question :)
< MarcoFalke> I don't understand the question, probably.
< sipa> MarcoFalke: he's trying to change the translation locally, but it does not seem to have an effect
< sipa> no release involved abywhere
< MarcoFalke> After you update the _de.tx file, you need to build the gui again
< sipa> unfortunately, i don't know anything about gui or translations, so i can't help :)
< madu> how do I rebuild the gui?
< madu> I changed the .ts file, through lrelase I got a new .qm file
< madu> with make clean i cleaned everything and build everything again new with make
< madu> but still its the same gui
< madu> hmm
< madu> hmm
< madu> now its working
< madu> dont know why.. but its working.. yess!
< madu> thanks
< sipa> madu: congrats :)
< GitHub128> [bitcoin] MarcoFalke opened pull request #7722: [qa] Use python2/3 syntax (master...Mf1603-qaPy2/3) https://github.com/bitcoin/bitcoin/pull/7722
< Luke-Jr> wumpus: are you going to do the v0.10.5 release, or should I take over 0.10 branch?