5400+ entries in 0.016s
mod6: phf: i thought last time we encountered a problem like this we dropped out a vpatch, then it was fine.
mod6: 'vtools_fixes_static_tohex.vpatch' is not the only one to be dropped out, so is 'vdiff_sha_static.vpatch'; i didn't notice on the first pass.
mod6: there is more going on here.
mod6: this is different than what i'm saying. the two distinct vpatches, 'vdiff_sha_fixes_newline_gcc.vpatch' and 'vdiff_fixes_newline_gcc.vpatch', contain the same output, '98ba7212fafa4a61f6d6096f1a2953a67a70fcf185965ed7199a223f6897c9b9f2996d391a3f363282236889413973d0beada0e36d57068549bea672fd110d8d'
☟︎ mod6: i'd have to fully debug the problem here, im only showing the symptoms here.
mod6: and a good question, is this a problem for 'theory of v' ?
mod6: <+mircea_popescu> oh, they don't, they just have the same antecedent. why is this a problem ? << im not sure at this point. could be an edge case im not catching, or could be buried in old rules built into my v.
mod6: 'vdiff_sha_fixes_newline_gcc.vpatch' and 'vdiff_fixes_newline_gcc.vpatch' indeed have the same output hash.
mod6: I'm not sure how to reconsile this. If you have a different v tool that will help you work around this, by all means.
mod6: one will notice that these antecedent origins are from two separate press-paths.
mod6: 6) We're not missing an antecedent vpatch; however, '98ba7212fafa4a61f6d6096f1a2953a67a70fcf185965ed7199a223f6897c9b9f2996d391a3f363282236889413973d0beada0e36d57068549bea672fd110d8d' matches two antecedents
mod6: 5) Check the origins of the antecedent hashes in 'vtools_fixes_static_tohex.vpatch' to see if we're missing one.
mod6: 4) Check the press paths -- there are ~two~ (phf said this was experimental previously)
mod6: 3) Check the flow, see that vtools_fixes_static_tohex.vpatch is not in the flow, and check to ensure that the seal verifies, and it dows
☟︎ mod6: 2) Once I have all the files, I put them in the proper place. Then grab the latest V (99993) and verify that it's correct.
mod6: and i've found the issue.
mod6: yup, i see the same.
mod6: ok, update to 99993 K plz. not sure it'll solve ~this~ problem yet.
mod6: hanbot: can you tell us what version of v.pl you are using?
mod6: yeah, but v.pl isn't picking it up, for some reason; i'll get to the bottom of why.
mod6: which is where the error comes from. im getting all of his patches & sigs and will see wtf
mod6: well, 'vtools_fixes_static_tohex.vpatch' is not found in her flow.
mod6: heheh, just figured I'd follow lobbes' lead there :]
mod6: !!v A6331853F44B13AB77F0A33CB3F6AAA9C9A7A212432EB20567803EA4F31E4117
mod6: !!invoice ben_vulpes 0.09169539 2 x Samsung EVO 860 1Tb SATA III SSD (2018.04.05) For S.MG box.
mod6: trinque: happy b-day man :]
mod6: made up name, say it out loud.
mod6: Hey, thanks for your donation shinohai!
mod6: ah, alright. will keep that in mind.
mod6: douchebag: ah just through april tho?
mod6: mircea_popescu: aha, iirc he said he's moving tho
mod6: instead of the united retards
mod6: iirc this dude would be coming out of eastern europe.
mod6: meanwhile, we should probably replace that bot functionality asap. we need a way to get VWAP recorded in here daily.
☟︎ mod6: shinohai, if you could bring that thing that'd be nice.
mod6: lol derp, this for some reason didn't occur to me lastnight. aight nevermind.
mod6: Or, w/e, s.nsa site should be coming back shortly anyway.
mod6: oh btw, the fg-genesis.vpatch and corresponding sig are not available via the archive.is link (originating from loper-os.org) ; You may want to post these some where accessable. I can throw them onto mod6.net if you like.
☟︎ mod6: thanks for the post asciilifeform
mod6: hey neat, i'll give this a closer look here tonight.
mod6: cool, an example of this that we can use to examine would be hugely helpful.
mod6: Maybe I'm a bit biased. heheh. there are still problems to tackle tho - and it's difficult to do so without adding further complexity.
mod6: Eitherway, I've become to like how we have it now.
mod6: alright, i'll have to take your word for it ; im imagining some huge diffs.
mod6: anyway, ok moving on..
mod6: it would also get nasty each time you remove or add a file in here.
mod6: or am i still missing this?
mod6: OH. i see what you're saying. so in stead of a & b per file, you're saying a & b for ~entire~ vpatch
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
mod6: vpatches were meant to be digestable.
mod6: one file, != fits in head
mod6: more generally: is a manifest part of a code-base
mod6: ok, so that would solve some of the 'hairyness'. a True Vpatch ~MUST~ edit chronicle.txt.
mod6: oh, and it just dawned on me how it would be np-hard to walk it backwards.
mod6: asciilifeform: ah, i figured we had probably been here before. cheers.
mod6: aha, and was changed.
mod6: it used to be in my V 99994 i would just blindly press all of the leaves, but that's was rejected as not the right thing. but with the good changes that 99993 brings in, could let the user choose at press time. just food for thought.
mod6: i.e. : `./v.pl p v outputdir gimme-all-leaves`
mod6: what if ole mod6 put in a special flag for that "gimme-all-leaves" instead of the listing of all?
mod6: you're saying if there are 69 leaves, and you want them all, then you have to list them all?
mod6: and if not, then user just selects one leaf, as is today. i dunno, would need some thought. i may be missing the mark here too.
mod6: then would press both trees
mod6: was thinking, that if we changed up the parameterization of v, could maybe resolve the multiple leaves thing. imagine
http://www.mod6.net/sps2_dag.png without the 'j.vpathch', if one wanted to press both trees, maybe could tell v to : `./v.pl p v outputdir i.vpatch d.vpatch`
☟︎ mod6: i've been thinking about the manifest thing for a while... and I'm not sure about it... seems like it'd get hairy. and would require versioning in and of itself. however, if we had a sample to look at, might be easier for me to grok.
mod6: (unless you really want my seals)
mod6: I do have seals for these signed with my vpatch-testing key... but you can just sign them with your junk key if you wanna play around
mod6: Think I mis-typed the above too: *like no pressing of descendants if all antecedents are ~NOT~ present in the current tree*
mod6: files are in the second link above if curious
mod6: Became necessary when testing for things like multiple roots, mulitple leaves; and have automation to break the tree into parts so I can ensure of other things, like no pressing of descendants if all antecedents are present in the current tree.