343600+ entries in 0.228s
BingoBoingo: Prolly n00b raised in
the school of "EVERYTHING AT ONCE"
assbot: Logged on 14-07-2015 19:24:25; ascii_field: 'why not start small, he said, offering
the yoga n00b a single nail'
assbot: Logged on 29-01-2016 07:42:24; polarbeard: I've
timestamped and categorized
trb log lines, as well as improved
the messages and removed (seeming never activated) destructive log rotation, here is
the signed patch:
https://gist.github.com/polarbeard/961aa315c69b89d2e613 in case somebody with a decent reputation wants
to review it so I can submit it
to
the ml
BingoBoingo: But
the RPC snip possibility is a beautiful side effect
assbot: Logged on 29-01-2016 06:06:33; mod6: "Eventually we can migrate
the whole RPC orchestra
to
this." << seems reasonable.
BingoBoingo: <ben_vulpes> repubtards are gonna say "los federales gunned down a confused old man stumbling around in
the snow!" << Old might have been
the serious problem. Perhaps
these men started
too late
to get
the actual RUF sorta militia mindset.
Turns out Kony was right.
punkman: ideally
turdatron would press all
the possible HEADs and let us see
them in lxr
☟︎ jurov: not anything serious, just
throwing some ideas.. looks like
this needs
to be revisited only when I encounter
the situation actually :D
polarbeard: gpg will
tell you when it was signed, you can use
that
to discard old patches
jurov: so v will complain and user will have
to resolve it by hand
punkman: they'd conflict, can't be in same
toposorted list
punkman: I
think it'd be best
to name
the 2nd patch mempool_frobsv2.vpatch or something like
that
jurov: wouldn't
that cause confusion when other files stay
the same?
jurov: and
the version field as just advisory indication which is
the more recent patch
punkman: btw, does
the
turdatron use v.pl?
polarbeard: ftr, I've updated
the gist, will send
the patch
to
the ml later
jurov: care
to share and watch
them burn?
jurov: perhaps you're new and full of ideas
to improve bitcoin?
jurov: I know
that i should manage
the repository myself, but imo a version field would be good
to have so
that I can easily spot if someone posts revised version of
the same patch.
☟︎ polarbeard: I appreciate
the suggestion, I'll just finish ensuring each line has priority and category and I'll submit
then
jurov: you will get more attention
there
than in
the log, and you can always post an update
polarbeard: thanks, I'll wait a bit for reviews I
think
jurov: polarbeard: i've updated ml, you can now post
to btc-dev
jurov: mod6: is
the V ..er.. V-ified?
punkman: so shiva patch wholly includes
the
tinyscheme genesis instead of referencing it?
☟︎☟︎ punkman: (by filter I meant "don't save
these lines", but I guess still useful when you are grepping or scanning with your eyes)
assbot: Logged on 29-01-2016 01:15:23; asciilifeform: or hm, does cpp string class allocate a fresh
turd when returning ?
polarbeard: me neither, but for
the amount of data it needs
to be introduced it won't hurt
punkman: that said, I'm not sure any
trb users will actually want
to filter on <priority>
polarbeard: yes, you're right, I'll add priority and category in each line,
thanks for
the observation
polarbeard: punkman: I wanted
to categorize
the information before prioritizing but it makes sense, in fact some server software (mongodb for instance) does
this with double prefixes using
this format: <timestamp> <priority> <category> <message>
punkman: so
the log lines are now prefixed with
two
types of
things: ERR INF WAR and MEM ADR BLK NET WAL. If you are gonna do
this it'd be nice
to have
the usual log levels on all lines (error,warning, debug, info) , so user can choose how much verbosity he needs.
assbot: Logged on 29-01-2016 08:13:49; ben_vulpes: definitely split
the actual muntzing out into its own patch instead of complecting it with
the rest of
the work. i might be able
to read and meditate on
that patch.
ben_vulpes: polarbeard: do i still fail
to make myself clear?
ben_vulpes: removing dead code is good, far better
than rewriting
the log lines. just split it out so
that it can be reviewed seperately from
the
two
thousand five hundred and ninety odd other lines of
that patch.
polarbeard: you want
to keep it? most people said it never gets activated
ben_vulpes: definitely split
the actual muntzing out into its own patch instead of complecting it with
the rest of
the work. i might be able
to read and meditate on
that patch.
☟︎ ben_vulpes: he also wanted
to
tabbify
the whole
thing
polarbeard: if not
that's fine, I built it for me,
the categorization was a nice idea from mp,
though
polarbeard: somebody has
to review it anyway, so I'll wait for any interest
ben_vulpes: "this 2.6kloc patch rewrites every log line in
the reference implementation, in support of further work i'm doing on" etc etc
☟︎ ben_vulpes: hell, submit it
to
the ml for posterity, i believe you have
the wot rating for
that.
polarbeard: I just felt it was fair
to anounce its existence
ben_vulpes: the problem with a patch of
this size is
that my face wearies of reading myriad log lines changed for seemingly aesthetic reasons, and i fear
that even a close read will miss an underhanded c contestant.
ben_vulpes: what you want
to reconstruct full state at any point in
time?
polarbeard: nothing, but gdb is for debugging
the present state
polarbeard: it
truly is, as what value it has, it's just a step into better debugging capabilities, for
this patch I've not added new log lines on purpose but I plan doing it for
the next
ben_vulpes: one develops a sense for what happens where in
the codebase watching logs.
ben_vulpes: and for what it's worth i actually like seeing
the function names in
the logs. i know i could just grep for
the log messages, but it's another way
to get familiar with
the codebase.
ben_vulpes: that is a lot of delta
to review for i don't precisely know what value
ben_vulpes: this'd probably be best delivered as 2 vpatches: one where you rearrange
the deck chairs in
the log messages, and another where you muntz out
the rotator
ben_vulpes: repubtards are gonna say "los federales gunned down a confused old man stumbling around in
the snow!"
ben_vulpes: unless
they shot him before 9:30 his hands are at his waist
ben_vulpes: look closer, danielpbarron, watch like
three more
times
danielpbarron: wow, pretty sure
they'd have gotten away if
they just ran over
the fed
that jumped infront of
the
truck at
the last second
mod6: "Eventually we can migrate
the whole RPC orchestra
to
this." << seems reasonable.
☟︎☟︎☟︎ mod6: are
these
the only
two implemented
thus far?
ben_vulpes: ugh mircea_popescu's line about software only working at a point in
time is so entirely fucking
timely
ben_vulpes: the WHOLE MOTHERFUCKING WORLD is conspiring
to rip
the rug out from otherwise entirely stable software
ben_vulpes: also restarting
the computer fixed "Photos"
ben_vulpes: "it's
to ease context-switching" devs in
the room witnessing my astonishment attempt
to
tell me
ben_vulpes: and lo a url i was just looking at in chrome on
the phone opens in chrome on
the browser
ben_vulpes: i click
this chrome icon out of a morbid fascination
ben_vulpes: so
today i open my bezzleputer, and discover a SECOND DOCK
assbot: Logged on 24-08-2014 21:40:36; *: asciilifeform had a dream many years ago
that his grandfather
took an ancient grinding wheel from workshop,
turned it upside-down, and
taught him
to ride it. and now people actually do something quite like
this.
BingoBoingo: asciilifeform: Honestly it looks like
they should get bonus points for emulating "grown up" candidates so well
BingoBoingo: Fucking Mizzou's still going more Oberlin
than actual Oberlin
mod6: i'll give it a go as soon as I get
the soba out and
test
the PVS.