298 entries in 0.403s
fluffypony:
polarbeard: I once met <insert name here>
fluffypony:
polarbeard: your wish has been granted!
assbot: Logged on 07-02-2016 15:33:02;
polarbeard: mircea_popescu, asciilifeform, ben_vulpes, mod6: a backport for sendrawtransaction rpc command,
phf:
polarbeard: hey, do you mind linking to your pgp key
ben_vulpes: ^^ asciilifeform, mod6, phf,
polarbeard, mircea_popescu: if any of you are willing to explain the inscrawkutable vdiff to my maleducated self i'd be much obliged
mod6: In regards to the above email section 0x04: To test this, one can simply grab
polarbeard's vpatch and sig and drop them into place, then try to press the entire tree. This should hault throwing an error since the actual output hash does not match the ~expected~ output hash.
assbot: Logged on 03-02-2016 18:52:30; phf: so there's two sig's that are not sha512. genesis.vpatch.trinque.sig is sha256 and polarbeard_add_getpeerinfo_rpc.vpatch.
polarbeard.sig is sha1
assbot: Logged on 03-02-2016 17:56:08;
polarbeard: oh, now I see the complete picture
assbot: Logged on 03-02-2016 17:30:57;
polarbeard: otherwise just check the sig date using pgp, last patch wins
phf: so there's two sig's that are not sha512. genesis.vpatch.trinque.sig is sha256 and polarbeard_add_getpeerinfo_rpc.vpatch.
polarbeard.sig is sha1
☟︎ ascii_butugychag:
polarbeard: because sigs submitted arbitrarily later than the patch !!!
assbot: Logged on 03-02-2016 00:15:59; mircea_popescu: actually
polarbeard if you're looking for more backportage stuff to do ... rawtx thing.
assbot: Logged on 03-02-2016 00:15:59; mircea_popescu: actually
polarbeard if you're looking for more backportage stuff to do ... rawtx thing.
phf: well, the idea is that you want to click on the patch and see how to press it. if i were to click in polarbeard_* presumably i want to press the tree that includes old malleus?
phf: kek, i know why polarbeard_better_log_messages don't press. it depends on asciilifeform_malleus_mikehearnificarum, which is replaced
phf: jurov: like
http://btcbase.org/patches/polarbeard_fix_instance_print , asciilifeform_malleus_mikehearnificarum asciilifeform-programmable-versionstring don't press because presumably conflict with programmable-versionstring malleus_mikehearnificarum in order. no idea why polarbeard_better_log_messages polarbeard_fix_instance_print don't press though
BingoBoingo:
polarbeard: And after rawtx ported Scheme X11 widget for interacting with shiva over rs-232 would totes make Gavin all Jelly
mircea_popescu: actually
polarbeard if you're looking for more backportage stuff to do ... rawtx thing.
☟︎☟︎ mircea_popescu: <
polarbeard> that's it, I'm patching every .c on my disk together with F 1000 and compiling it << lmao. STONE SOUP!
punkman:
polarbeard: actually F0 didn't apply offset << it should, if you offset the code. but it must find the context verbatim
mircea_popescu: but as
polarbeard among others can testify, this makes writing code fucking difficult, thanks god.
mircea_popescu: polarbeard_add_getpeerinfo_rpc.vpatch and polarbeard_add_getpeerinfo_rpc.vpatch.mircea_popescu.sig in this order
mircea_popescu: ok so i am sending an email to btc-dev@therealbitcoin.org with subject line Certify polarbeard_add_getpeerinfo_rpc with content as a clearsigned short explanation of what it is, and with two attachments
punkman:
polarbeard: not bad, which version did you backport from?
assbot: Logged on 02-02-2016 05:08:04; mircea_popescu: so basically
polarbeard here's the thing : i considered signing this, and i will consider signing the next version. as it is however i won't do that, because a) not all errors have both flags set ; b) occasional ' in error message ; c) occasional losing a valuable datapoint (such as the hash above) or missing on adding a useful one (nStart).
assbot: Logged on 02-02-2016 04:41:22; mircea_popescu:
polarbeard + return error(SBLK "chain tip %s not found in the block index", hashBestChain.ToString().c_str()); << any reason this has only one flag ?
mircea_popescu: so basically
polarbeard here's the thing : i considered signing this, and i will consider signing the next version. as it is however i won't do that, because a) not all errors have both flags set ; b) occasional ' in error message ; c) occasional losing a valuable datapoint (such as the hash above) or missing on adding a useful one (nStart).
☟︎ mircea_popescu:
polarbeard + return error(SBLK "chain tip %s not found in the block index", hashBestChain.ToString().c_str()); << any reason this has only one flag ?
☟︎ ben_vulpes: well
polarbeard likes to pretend as though i don't exist until he finally does what i ask, and even then refuses to ping me on the topic.
phf:
polarbeard: you can't press polarbeard_better_log_messages directly on top of asciilifeform_maxint_locks_corrected period. so the ~transition~ makes no sense
phf:
polarbeard: it's not correct, since the graph is supposed to only show transitions, rather then descendants/antecedents. in this case polarbeard_better_log_messages touches util.h and util.cpp that are modified in polarbeard_remove_shrink_debug_file
phf: there's a bug of some sort, pretty sure your polarbeard_better_log_messages shouldn't press from asciilifeform_maxint_locks_corrected, i'll look into it tonight
mircea_popescu:
polarbeard i dunno that it was expected to either. prolly isn't, really. just, bitcoin code is too layered, random and messy.
mircea_popescu:
polarbeard mno, this is no good, it doesn;t solve the naked return problem. for instance (all from bitcoinrpc.cpp) : return error; at line 44 ; return "bitcoin server stopping"; line 162 sorta thing.
mircea_popescu:
polarbeard incidentally, did you leave any nude returns ?
mircea_popescu:
polarbeard aite. ima slog through this, mind you that it's 2k lines will take hours.
mircea_popescu: ok
polarbeard if you don't mind we'll use his version it's about 500 times better than github
mircea_popescu:
polarbeard do you have the tags you use enumerated anywhere ?
mircea_popescu:
polarbeard don't put commas immediately after urls it fucks things up
BingoBoingo:
polarbeard: But if you could write that funtionality in Scheme, you might get some love for it.
mircea_popescu:
polarbeard it won't hurt anything writing a backport patch for it if you feel like it.
mircea_popescu: asciilifeform and
polarbeard would much prefer large patches. you don't get what you prefer.
assbot: Logged on 29-01-2016 18:31:10; ascii_butugychag: mircea_popescu: it bothered me that
polarbeard apparently does not yet fully grasp that every line he writes is a unit of ~work~ for other people to do.
mircea_popescu:
polarbeard don't get this wrong, you did a lot of very useful work in that patch.
punkman:
polarbeard: the thing usually runs as a daemon
mircea_popescu:
polarbeard yeah, you get the right idea, but seriously, making a single patch consisting of JUST -return error +return error is the right way
ascii_butugychag: mircea_popescu: it bothered me that
polarbeard apparently does not yet fully grasp that every line he writes is a unit of ~work~ for other people to do.
☟︎ punkman: mircea_popescu: so how would you split
polarbeard's patch?