229100+ entries in 0.15s
phf: tee writes piped input
to stdout and
to a file
ben_vulpes: i would also like
to see
the vdiff into which you're piping diff, mostly out of curiosity
ben_vulpes: "tee p" just papers your house with
the output or what
ben_vulpes: good
to know
that
terminal prompt of yours survived
the
trip
through
the pastebin
ben_vulpes: would it be unreasonable
to calve
this scenario off?
ben_vulpes: 1
thing of note is
that your example patches an extant file in holyfuq/
mod6: i
think you maybe mean '-F' instead of '-f', it
thinks 0 is a file
phf: ben_vulpes: where'd
that 0 come from?
ben_vulpes: phf: i actually can't get patch c/old.lisp and d/veh.lisp
to apply derp.vpatch
mod6: anyway, yeah, as I said in #trilema-mod6, i see
this as low-priority and SUPER high risk. but I'm open
to suggestions how
to implement
this properly and safely.
phf: actually
that's a bad example because
that'll work, but a/old.lisp and b/veh.lisp
phf: so if you were
to produce a patch with a/old-veh.lisp and b/veh.lisp. existing vtrons will happily press it,
though it's a
total clusterfuck
☟︎ phf: patch/diff lets you have a patch with --- foo +++ bar in which case it seems
to ~check if foo exists,
then
try and press against foo, otherwise press against bar~
ben_vulpes: what's an insane input
that breaks
the shortest common substring
test?
phf: but i'm starting
to
think it's an overkill anyway, because it doesn't accommodate for all possible insane patch inputs.
phf: that's what btcbase does basically. it finds position where common suffix starts and
then works from
there..
ben_vulpes: would a smallest common substring
test suffice here?
phf: actually patch seems
to do ... something magical
phf: i
think it
treats one of
the names as canonical
☟︎ trinque: patch will ignore
the number of levels you specified with -p
phf: so
the simplest solution would be
to at least parametrize an equivalent of -p1 on lisp side
phf: ben_vulpes: well, we're kind of constrained by
the hardcode -p1 behavior, but i've no idea if
that's an implementation detail or a spec
ben_vulpes: the
third approach is
to apply each patch
to an empty directory and determine what files would have been patched, had it applied cleanly.
ben_vulpes: the only other
thing
that i can
think
to do here is
to grab
the set of parents and children, match
them up, and
then get
the lowest common denominator (if you will) file path for each patched file directly from
the vpatch
ben_vulpes: c) hash
that file and compare
to
the vpatch contents
ben_vulpes: b) when working
through
the list of each patch's children, search
through
the list of patched files until
the patched filepath is a subsequence of
the filename as recorded in
the vpatch
ben_vulpes: a) capture output of `patch'
to determine which files were patched
trinque: phf: when I brought
to you "whence
the disjunction between
the practical and
theoretical sides of subj" your output was "OP == faggot"
trinque: lol, but
then russians
take
the
thread wherever
they like without
telling anyone.
phf: also i learned long
time ago
that americans* aren't
taught how
to argue properly, so when
they do
they have a really hard
time keeping
the
thread, keeping more
than one point, developing an argument, bringing it back
to original point, etc. consensus intelligentsia are all very civil, so when you do get
them railed up,
they just flail, sort of discourages from even
trying
phf: hehe, as much? no. but
that's only because if
there's one lesson i learned from naggum, all
this rage is not healthy.
mircea_popescu: phf for my own curiosity, does anything in
the rest of your life piss you off as much in aggregate as one session with
these assholes ?
phf: well, (graphic-char-p #\space)
T phf: asciilifeform: i will have
to concede, (graphic-char-p #\newline) NIL
mircea_popescu: if it starts with picture it can't be a part of
this discussion.
mircea_popescu: we still didn't see
the profiling for
the symlink
thing\
trinque: could be. I'd like
to see
the design for such a
thing.
trinque: when I build
things
to ask
the fs how many customers in new york placed orders on
the weekend it starts
to look quite like a relational db
trinque: asciilifeform: aside "write a data manipulation environment
that provides what
trinque demands" I do not see a path here.
trinque: and I'm
tweaking
the site generator
mircea_popescu: trinque ok so can i get
this guy's key he's kinda weaiting for an acct.
trinque: asciilifeform: we poor bastards who made money living inside SQL find ways
to make it work.
mircea_popescu: and gtfo with
the inept simile,
the correct comparison is "imagine if your cock didn't work if
there was already one in
the
target woman". which i bet yours doesn't, so really.
mircea_popescu: asciilifeform
there would be
two
trees not "two genesises" in his idea, he's making a
tree for
the site and a
tree for
the
tooling.
a111: Logged on 2016-11-19 18:52 asciilifeform: Framedragger: db being hammered 24/7 with 'do we have
this hash' 'do we have
this fp' 'add
this and
this' 1000/sec is
the bottle.
trinque: noobs can aspire
to be named
there
trinque: I'll instead write
the page and exclude from
the index
trinque: mircea_popescu: ah you know what, excluding nicks with no ratings breaks
this, because writing
the keyfile happens inside
that logic.
mircea_popescu: trinque i
think
that's how pretty much everyone ends up doing
things.
trinque: that sounds like a bug, really, but
the kind of bug
the complexity of
the
thing makes hard
to remove
trinque: recall I conceded in
the bitcoinfs
thread
that what I consider
to be "database" is actually many orthogonal
tools related
to data manipulation, atomicity of operations, adherence
to
type constraints ~if desired~
trinque: as
the shell is a user interface, in
the first case
trinque: this is not
the direction from which
to come at
this subject
trinque: but
the right answer is as much or as little structure enforcement as you like.
trinque: wot.deedbot.org will likely result in
two genesis patches down
the line. one for
the
tool, other for
the particular site
trinque: asciilifeform:
the question answered here is "why regenerate
the same idiot HTML every www request?"
trinque: I am not using html as a data storage format what
the hell
ben_vulpes: trinque: just sed and awk
the html you have in place
to update ratings
trinque: and everything
to do with shitty html flowing from properly structured data
trinque: this model has nothing
to do with sql
trinque: asciilifeform:
that is precisely what I just said
trinque: asciilifeform: because people update
their ratings
trinque: there's a listening process consuming
these pg_notify events, of
the form (gen-nick-page "trinque") which debounces
them according
to some sane interval, i.e. if a few updates hit
the same user in a short span, it will result in one single rebuild