tmsr - Search: i

40500+ entries in 0.23s

phf: like i said, i understand the problem, i'm not sure of the solution, because ~i~ have not attempted to tackle it. for example i suspect that the manifest might be problem specific, i.e. what you put there is informed by the shape of the tree you're trying to create.

asciilifeform: i was somehow quite certain that trinque had a pseudocode-algo for his improved vtron

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

mod6: asciilifeform: ah, i figured we had probably been here before. cheers.

trinque: then perhaps I'm wrong. I'm trying to present a problem to you by way of examples and it's not taking.

a111: Logged on 2018-03-30 22:09 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`

asciilifeform: http://btcbase.org/log/2018-03-30#1791427 << i proposed this at one point, and mircea_popescu (imho correctly) barfed, and one of the reasons was that it makes pressing irreversible (or at least reverse-walking becomes np-hard) ☝︎

phf: trinque: didn't you accuse me of projecting before, ~where did i refuse to acknowledge this problem~

trinque: if returning to "press everything, don't specify HEAD" I don't see that there can be multiple lines of history (branches)

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?

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.

trinque: hm. I'd have to ponder a while to see what's lost. it's unclear what the purpose of designating a press head would be in that scenario

phf: originally this was \supposed to be solved by curated wot, i.e. all in-wot-dangling leaves that can be applied to current press, by hash, would get pressed

mod6: i.e. : `./v.pl p v outputdir gimme-all-leaves`

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: 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.

phf: though a manifest could be used as a kind of assert during press, as long as it doesn't rely on filenames. (i believe the idea of putting antecedent vpatch's hashes into manifest floated around)

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

phf: mod6: would you mind uploading that test tree somewhere? i want to throw it at btcbase. fwiw, vpatch/vdiff doesn't care about press tree, as long as the hashes work out in the end

mod6: Think I mis-typed the above too: *like no pressing of descendants if all antecedents are ~NOT~ present in the current tree*

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.

mod6: I made a test vpatch set for v related development. Super helpful. Allows me to create test scenarios and automate them, ensuring that I'm not regressing from version to version.

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

phf: but i don't think i could've implemented ~patch equivalent~ differ in reasonable time. vpatch already ballooned out because of an unfamiliar development environment, and it's much less heuristic based.

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 ☟︎

mod6: fwiw, I think minus other targets, such as the empty dir thing, it's probably going to be easier to regresion test without changes for those targets -- basically having a 1:1 mapping of the old to new.

mircea_popescu: i have no issue with it, can be added now without any serious loss. the only thing not clear to me is whether you don't want to add it, can't add it yet or haven't gotten around to adding it yet.

phf: i grok that point; the things are simply not there. i've barely arrived to where i have a working replacement for what we already have on top of which further work can be built. i guess the only reason this one is contentious is because it would've worked better if done upfront.

mircea_popescu: the reason the list of firm targets doesn't include the soft "well, i'm curious what he does about X" is precisely because... how hard am i gonna push it ? that's kinda the constraint, on one hand death by vagueness & ambiguity, on the other death by insufferable overbearingness.

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.

phf: i'm not even through the list of target items yet, any one of them can be picked up as an example of "didn't bother to implement any solution for"

mimisbrunnr: Logged on 2018-03-30 18:36 mircea_popescu: reason i even did things in this manner is because it's not clear to me why it was contentious or whether the contention was resolved.

mircea_popescu: now, from the evaluation late march, it seems to me i was correct in thinking back mid dec that you understood what the problems are, but that you didn't bother to implement any solution for one of them ? or what am i missing ?

mircea_popescu: Dec 14 14:07:00 <mircea_popescu> maybe he bites the bullet and makes special files. or who the hell knows. i'm curious.

mircea_popescu: Dec 14 14:06:42 <mircea_popescu> i'm letting him contribute, what. he understands what the problems are.

mircea_popescu: um. no, i said as much months ago, dja want me to dig the log ?

phf: mircea_popescu: right, around the time when you made that mothballed comment did i get cued into the idea that you wanted me to implement it.

mircea_popescu: well, the vdiff new tree was originally the most promising point for such a sample. i did say something in the vein of "i'm not going to keep trinque mothballed forever if you don't do it" recently, but anyways.

phf: i don't understand the solution. i've spent significant amount of time writing various graph walking algorithms to feel like without an set of experimental patches it's hard to have a solution that actual address the underlying complexity. what i wanted to see from trinque or whoever's attempting to solve this problem, is an actual attempt to construct a press tree with a manifest file that does what they want, to ensure that the approach actual solves

phf: but spyked might also be running into a lateral issue, that's related to double presses. in any case ~i~ need to look at it first before i have understanding of it.

phf: i'm saying that i understand the meta problem, because i've seen other people deal with it, and there's been a lot of competing proposals as to how to solve it, including trb's "makefile" approach.

phf: i'm not sure if his analysis of the problem is correct without looking at it myself first

mircea_popescu: nono. i don't mean the direct, i mean the meta.

phf: mircea_popescu: i've seen that problem before, but i haven't tried solving it myself yet, because i've not ran into it. i've not had a chance to attempt spyke's problem/solution yet

mimisbrunnr: Logged on 2018-03-29 15:00 spyked: the way I understood it from reading v.pl, the edges in teh graph are established based on changes introduced by each hunk in the nodes (the patches). so since there are no patches changing the files in vdiff_lib_xalloc_static_xnmalloc.vpatch, it's a leaf (and this, if I understand correctly, is intrinsic to the current design of v).

mircea_popescu: reason i even did things in this manner is because it's not clear to me why it was contentious or whether the contention was resolved.

phf: i don't understand his idea

trinque: http://p.bvulpes.com/pastes/9g8Sl/?raw=true << sure, I think it's just the expected flow up to the current patch

phf: trinque: can you produce a sample then? i don't want to implement your idea, having only vague understanding of how it's supposed to look. there's been many discussions in the log as to what the actual manifest contents should include

trinque: not like I'd have been opposed; it's just easy to imagine what it'd look like. every patch has an antecedent of the history file, as well as whichever other files.

phf: a as to what format the manifest supposed to be. i didn't realize that the idea is that vtools tree was supposed to be the first one to experiment with it

phf: http://btcbase.org/log/2018-03-30#1791280 << it's an oversight. i thought that the idea is that my vdiff/vpatch support programmatically whatever manifest format we come up with, but somebody demonstrates how it's supposed to work first. it's not hard to regrind existing tree, manually add a manifest, and then see how it looks on a graph. for some reason i thought that trinque has that experiment in his pipeline, since he also seems to have a clear ide ☝︎

asciilifeform: ( the more frequent ending seems to be the one pictured in http://trilema.com/2013/and-then-i-said-to-him-jimmy )

mircea_popescu: i wonder which one of these identitties will pop up later doing anything worth the mention.

mircea_popescu: trinque i k r!!1

grimm: i just wrote what was given

grimm: https://i.imgur.com/5dDoHn2.jpg

douchebag: oh shes back as grimm I guess

a111: Logged on 2018-03-29 23:39 mircea_popescu: i suspect by now "autistic" is the equivalent of the 1800s "friend". "one of ours" as opposed to "one of theirs"

phf: mp picked up on your use of "autistic", which i didn't grok myself http://btcbase.org/log/2018-03-29#1791068 ☝︎

a111: Logged on 2018-03-30 05:00 ave1: mod6, well your environment is sound and exactly the same as mine. Also you get the same error. Spyked patch should fix it (or open lib/xalloc.h and add static to all inline void functions that do not already have a static). It may be that phfs' enviroment is different (so far as I can see, spyked, hanbot, me and you all have the same problem).

phf: http://btcbase.org/log/2018-03-30#1791228 << i'll publish the relevant patchsets on btcbase this saturday; i've read the relevant specs and the issue seems to be straightforward, what is annoying though is that for whatever reason it's not uniform across platforms. ☝︎

douchebag: alright, she's offline at the moment. I'll let her know whenever she decides to get on

mimisbrunnr: Logged on 2018-03-30 06:14 douchebag: I was wondering, how much would I earn from writing qntra articles?

ave1: and another typo (i'm sorry) -> diana_coman

ave1: diana_comon, Yes, I read the test and the code and your text (also played with the test a little). So I was a little suprised that rsa_oaep_encrypt used mpi code. I will write an alternative.

mircea_popescu: aand in other morning glories, "i dreamed that i was in trouble, i don't know what, and i was walking back to where you were, shaking incontrollably from all joints. but then, voice-of-god you, that was in the air, said "don't worry about it, pet. go back to sleep". so i went back to sleep." "did i also look like the old king on the packaging of small chocolates ?" "no, you didn't look like anything, it was just the voice."

diana_coman: to answer your question directly though: 1. it certainly could - rsa_oaep_encrypt is just a wrapper so it's meant more as an example of using all the stuff together rather than a standard: I'd expect that there would be other/different wrappers, made to suit specific uses

douchebag: No I'm not in there, can you give me a brief overview of what's going down?

douchebag: I assumed mpex.biz but since that's down at the moment I wasn't able to verify

ben_vulpes: man i don't know anything about port but this is delicious

douchebag: I was wondering, how much would I earn from writing qntra articles?

douchebag: mircea_popescu: I have a girl but she is wondering if she's allowed to wear sunglasses ☟︎

ave1: btw I tried adding -flto/-fno-lto flags and optimization flags, but these did nothing for me.

ave1: mod6, well your environment is sound and exactly the same as mine. Also you get the same error. Spyked patch should fix it (or open lib/xalloc.h and add static to all inline void functions that do not already have a static). It may be that phfs' enviroment is different (so far as I can see, spyked, hanbot, me and you all have the same problem). ☟︎

mircea_popescu: i dunno wtf is it with sketchers, but they're the sketchiest bunch by far.

ave1: mod6, I'm sorry I forgot the project name(http://btcbase.org/log/2018-03-30#1791071), this should do the trick: gprclean vdiff.gpr; gprbuild -v vdiff.gpr ☝︎

mircea_popescu: in case this is the last you hear of me -- know i've had a good life.

mircea_popescu: it is now in the freezer. i'm having the third serving. best 300 calorie spoonfulls i ever had.

mircea_popescu: AND THEN i cooked the flour in the fat and bechamel'd it with the alcohol. the resulting sauce got poured over cut up bananas.

mircea_popescu: in other suicide notes : i had girl grind into fine dust a 100% chocolate bar while another ground into similarily fine dust semillas de maranon. i myself was dumping raisins into rum.

douchebag: I see, I guess I'll just try to find a prositiute who knows how use a computer

douchebag: but I could easily round up a couple prostitutes and have em write on their tits

douchebag: mircea_popescu: Hey I was wondering, I know a shit ton of prostitutes - do I get 0.02 in exchange for their tit pics?

ben_vulpes: i am pantsuit, see me signal

ben_vulpes: i know i know

trinque: ben_vulpes: lol coals. I paid the damned thing before I even saw.

ben_vulpes: trinque: http://p.bvulpes.com/pastes/xmnNW/?raw=true i can provide dates and conversion rates if you really feel like raking me over the coals

mircea_popescu: and this is, incidentally, why i don't for a second believe "alt-right" is anything but alt-socialism ; or why i never looked with friendly eyes upon say modlbug.

ben_vulpes: mircea_popescu: i don't understand the point in re male regulation of the copulation rate

ben_vulpes: huh i don't see the lineage from straightedgin; but my only brushes with it were kids who thought they needed something to differentiate themselves from oh okay now i see

mircea_popescu: ben_vulpes i think alt-right is more a continuation of "straightedge" 90s fashion than any kind of 1950s wasplandia.

ben_vulpes: here i was thinking, "hm i wonder when the girls will actually start dolling up"

douchebag: Too bad I don't have a bullwhip like mircea_popescu

douchebag: I tell these women, when they get the code to have the photos ready within 5 minutes

mircea_popescu: but, truth be told, the reason i keep asking about previous work is precisely this. aaanyways.

douchebag: I'm just wondering how that sorry execuse for a tit pic took a whole fucking hour

douchebag: i think it's one of them cheap phones mexicans have

mircea_popescu: i thought the whole point of "smart"phones was the camera.