2500+ entries in 0.081s
mircea_popescu: the good news for you mod6 being that you don't really have to do anything ; v.pl is fine as it is, for now, and once
phf has a prototype walker you can just move on to that and it'll be cheaper. continue work on your ada guy in the meanwhile at your leisure, seems we're converging that way.
mircea_popescu:
phf i guess next on your plate is make a prototype proper grapher for all time ? then mod6 can put that in v and avoid further such wtfs.
☟︎ mircea_popescu: yeah. so on one hand indeed the problem was as suspected ; but on the other hand
phf is correct and yes the graph IS constrained.
mod6: mircea_popescu: i can try the leftmost trunck on
phf's viewer, but not right this minute. maybe in a few hours. i'm pinned down in the mud. gotta kill the guy in the pillbox first.
mircea_popescu: a right. hanbot do me a favour : download ~only~ those patches which are in the leftmost trunk seen on
phf's viewer (so exclude vtools_vdiff_sha, and its dependents) and try to flow again ?
☟︎☟︎☟︎ mircea_popescu:
phf what is the vdiff_sha_fixes_newline_gcc link to vtools_fixes_static_tohex ? as now apparently the two patches are entirely disjunct, did you update or something ?
a111: Logged on 2018-04-09 13:59
phf: antecedent graph != requirement graph
a111: Logged on 2018-04-09 04:25 hanbot:
phf et al: attempted to press latest vtools to the keccak head. v (mod6's) reports vtools_vpatch_newline not in flow, neither its antecedent vtools_fixes_static_tohex, despite both patches and (verified good) sigs present (they neither show up via flow command). v will press to vtools_vpatch.vpatch, but no further. see
http://p.bvulpes.com/pastes/oNRhE/?raw=true .
mircea_popescu:
phf oh! it tries to press vdiff_sha / etc because they're actually a dependency for tohex ?! why did you write it this way ?
mircea_popescu:
phf it's incomprehensible to me as the manifest.txt varies wildly.
mod6:
phf: i thought last time we encountered a problem like this we dropped out a vpatch, then it was fine.
mod6: 4) Check the press paths -- there are ~two~ (
phf said this was experimental previously)
hanbot: not sure if this has something to do with the note in
phf's accompanying release post re btcbase presser not working quite right....
hanbot:
phf et al: attempted to press latest vtools to the keccak head. v (mod6's) reports vtools_vpatch_newline not in flow, neither its antecedent vtools_fixes_static_tohex, despite both patches and (verified good) sigs present (they neither show up via flow command). v will press to vtools_vpatch.vpatch, but no further. see
http://p.bvulpes.com/pastes/oNRhE/?raw=true .
☟︎☟︎☟︎ a111: Logged on 2016-09-25 01:47 mircea_popescu:
phf 64.86.243.181, 130.239.18.119, 164.132.77.237, 139.162.227.51, 91.217.189.42, 38.229.70.22, 82.96.64.4, 195.154.200.232, 185.30.166.38, 162.213.39.42 << pick from there
mircea_popescu:
phf it means it does not map to any sort of rational, coherent, non-contradictory model of the world.
a111: Logged on 2018-04-06 21:19
phf:
http://btcbase.org/log/2018-04-06#1793646 << i'm moving too slow, please wait till tomorrow for me to push the regrind with fixes. if you can give me that version of mp-wp.vpatch unsigned that would be helpful
a111: Logged on 2018-04-06 19:35 hanbot: latest in mp-wp saga: spyked's patch on vtools let me gpr build the
phf's patcher and vdiff, latter of which made a genesis, former of which dies on pressing wiff:
http://p.bvulpes.com/pastes/2IVPp/?raw=true a111: Logged on 2018-04-06 17:35
phf: they are more of a suckless spinoff
TomServo: asciilifeform: perhaps I've been too generous... perhaps..
phf has it.
TomServo: I fell down the gopherhole after
phf mentioned it.. came across a pseudo-tmsr 'bitreich'.
a111: Logged on 2017-11-23 16:20
phf: re upstack, there's been a resurgence of sorts of gopher protocol, various hipsters spinning up personal websites, etc. whether the resurgence was shortlived or i'm just late to the game, but there's already a community of wreckers (one of them groups is coming from this federated twitter platform, mastodon) discussing all the various ways that they want to "improve" gopher, tls, utf-8, markdown renderer, "minimal subset of html", etc. but at the same
a111: Logged on 2018-04-04 00:35
phf: i did several talks on the idea that sanitizing data is retarded, and that you're supposed to have a proper parsing strategy instead. that it's in other words an impedance mismatch problem, and if you teach computer your assumptions it will be impossible to have injection issues
a111: Logged on 2018-04-04 00:46 asciilifeform:
phf: i was vaguely hoping he might grasp this by playing with pehbot / reading ffa ; but loox like no dice so far
mircea_popescu:
phf it's supposed to produce no more than one line per command.
a111: 2014-03-20 <
phf> not quite
a111: Logged on 2018-04-03 23:41
phf: mircea_popescu: "Unlike obligate coprophagiacs, subsistence hunters could not be stone age fucktards, but for whatever reason opt not to." is there a double not in there?
lobbes: well, it seems like
phf's (and others') approach is slightly saner. Even if user input doesn't go to bash, well.. what about the phantomjs exploit you found
a111: Logged on 2018-04-04 00:35
phf: i did several talks on the idea that sanitizing data is retarded, and that you're supposed to have a proper parsing strategy instead. that it's in other words an impedance mismatch problem, and if you teach computer your assumptions it will be impossible to have injection issues
douchebag:
phf: What sort of topics do you primarily focus on?
mircea_popescu:
phf still though, losing out on threading on a quad machine is a little dumb.
mircea_popescu:
phf that's the issue in my head, of no practical consequence as it is : why, exactly, different beast, and how ?
mircea_popescu: at which juncture i suppose it'd pay to check, huh. hey
phf, my memory of logs discussion includes this item whereby the above problem was fully resolved by declaring the path as inseparable part of the filename. you on the same page ?
☟︎ mircea_popescu: ah. so then get the whet back and see from there. maybe new vdiff is ready ; if not and you want to march you can apply spyked's patch on the extant codebase as published by
phf, if i understand correctly that should fix your problem. the diffs you produce with the thing thereby compiled will work with later restared vdiff too.
mircea_popescu: hanbot atm
phf is re-grinding his vdiff to include histfile and afaik you didn't have hosting ? did that meanwhile resolve ?
mircea_popescu:
phf kinda what that ended up with, "let's see how deep it can possibly get"
mircea_popescu:
phf see, it never stops. it's not something one can turn off at will, sadly.\
mod6: <+
phf> problem can also be solved with having entire project in one file, << to me, was trying to picture trb one giant vpatch, over and over, may have misunderstood
mircea_popescu:
phf i don't get it, why would we adapt the way we do things to what'd be convenient for the machines ?
mimisbrunnr: Logged on 2018-03-30 22:15
phf: trinque: i'm describing how things are right now, how things were, and what informs my and mod6 opinions on the subject. uncertainty about past behaviors in my opinion tends to influence uncertainty about future solutions
mimisbrunnr: Logged on 2018-03-30 22:13
phf: trinque: there's no "returning to", original behavior is "press everything that falls from under this head"
trinque:
phf: there are cases where two separate edits to separate files are both needed as antecedents to yet a 3rd patch, which edits possibly neither of them.
trinque:
phf: where are you at on the practical problem of "trinque wants to redo portage in V" and I don't want people giving me patches that include unrelated ebuilds?
trinque:
phf: can you elaborate a bit?
a111: Logged on 2018-03-30 20:47
phf: the retrospectively unpleasant part of this approach is patching vdiff's C, which, after writing a bunch of Ada, is torture. i believe diana_coman had similar experience
mircea_popescu:
phf i'm not saying you're the badman, or that it was necessarily plainly communicated. but, for what it's worth, that's what it was there.
a111: Logged on 2017-12-14 22:49 mircea_popescu:
phf so basically this is cropping down nicely after all. proper vpatch (fixing mod6 's bane, the empty dir thing) + proper vdiff (hash-based preprocessing of rename/move + proper use of @@...@@ + keccak hashing).
mircea_popescu: you,
phf, made genesis G, with files a, b, c. you then made patch 1, which changes file a.
mircea_popescu:
phf do you see the problem spyked's patch to your v tree encountered ?
mircea_popescu:
phf that's the whole fucking point, implement his idea, having only "vague" understanding of how it's ~supposed~ to look. then he can comment on it.
mimisbrunnr: Logged on 2018-03-29 14:53 mircea_popescu: is this deliberate or oversight
phf ?
mimisbrunnr: Logged on 2018-03-29 14:53 mircea_popescu: is this deliberate or oversight
phf ?
spyked:
phf's ld might add an "static" to "inline"; or not, not sure; can verify by objdump'ing vdiff and seeing if there appear multiple (with local linkage) definitions of xnmalloc in the same file.
☟︎ a111: Logged on 2018-03-28 20:41
phf: hmm, i wonder if adacore's gprbuild uses its own gcc or global one
a111: Logged on 2018-03-28 20:41
phf: hmm, i wonder if adacore's gprbuild uses its own gcc or global one
mircea_popescu:
phf don't you wish this shit existed when we were 15 ?
mod6: so here's the deal, your vpatch & sig do verify by hand, so that part is fine. the problem lies in the fact with all of
phf's vpatches in your 'patches' directory, your vpatch tries to come from two separate antecedents.
a111: Logged on 2018-03-28 20:37
phf: mod6: pressing to different tails should produce alternative builds without any conflicts. but the issue has been discovered, and it requires a patch. spyked originally found both the problem and the solution
mod6: So there are a few things that I probably should ask about, as it wasn't wholly clear to me about the pressing side of things. Since there are multiple roots, and multiple leaves, there are two different press paths. Now, maybe I'm not supposed to have all of these in there?? But it looked to me from the thread at
phf's site, that I needed to have them all.