16400+ entries in 0.043s
mod6: <+shinohai> mod6: new trb is at height 284171 << good deal, thanks for reporting :]
mod6: anyway, will re-walk through this all again tonight, etc. then will sign and send to ML.
mod6: ben_vulpes: here's a peek at the squshed beta 1 & beta 2 vpatches - unless something changes between now and tonight, i'll be sending this one to the ML. All you need to do to apply is get V [v99996], copy `v.pl' to `v.pl.v99996`, then place this patch in the same dir and do: `patch -p0 < V_v99995_beta2.vpatch` and give it a go
mod6: i updated alot of the automate tests, and added a number of them, to ensure that i didn't regress anywhere. so far, seems good.
mod6: will basically encompass what will be v99995
mod6: shipping? it'll just be a whole bundle once we do a bit of testing -- but tonights patch will be a squashed patch of the one from last week, and the additional changes here.
mod6: if/when you can get the new patch applied, give it a try and let me know. thx.
mod6: <+ben_vulpes> press a patch without hashes in the headers << i've actually got that one covered in the patch im about to put out there tonight.
mod6: im just gonna leave what i've got in there. will replicate what alf's does.
mod6: anyway, doesn't matter for now anyway.
mod6: <+mircea_popescu> mod6 im not even sure we can depend on a notion of "time" for v purposes. << oh yeah 'the last time' is probably a bad choice of words, "the last alteration" or some such.
mod6: ok, i'll leave origin in for this second beta patch.
mod6: s/from origin/since genesis/
mod6 is just pondering weather the converse is useful. finding the last time the file was changed from <given> hash
mod6: this will give us when the hash was introduced, not the last time it was changed.
mod6: and just to verify, we *do* want to be looking at the post-patch hash value correct? the 'b' as opposed to the 'a'.
mod6: I've basically just added the corresponding source file in the data there.
mod6: shinohai: ok thanks for the update. let us know how it goes.
mod6: mircea_popescu: the reward for the Block Cipher contest
mod6: also, which block was the last accepted? i.e., which block was it grinding on?
mod6: gernika: be sure to capture logs. we've seen wedges in the past, and they hvae some distinct tell tale signs in the logs.
mod6: i don't think a billion units is lulzy at all.
mod6: wouldn't wanna make me stab myself in the face any less.
mod6: that shit isn't right, especially before you've had your coffee
mod6: this morning I had to nearly step over two hobo's fucking in the trainstation.
mod6: A great idea, overall. Thanks for posting that and putting up the reward.
mod6: nice i threw it out there in the twat space
mod6: in this case, V will return an error stating something like this: HEAD: asdfasdfasdf not found in flow
mod6: alright, i've got a local fix for gernika's bug where it'll press the entire tree out if the given vpatch is not in the flow.
mod6: yeah, i agree. im hoping that after this round of fixes in place, that the mission-critical features are solid enough to warrent a genesis.
mod6: I've got a local fix in place for ben_vulpes' error that he brought up: A file (of any type) exists in 'patches', and it causes V to fail ungracefully.
mod6: but yah, in general, it should have its own tree of vpatches. and will save me a lot of pain too :]
mod6: thanks for your patience, Mr. P. & all.
mod6: but not for at least a week. i need some time to look into that and to let people test the beta patch. i want to get these resolved so we can move on.
mod6: so yah, if i can get something figured out for that bug, maybe there will be a beta2 patch.
mod6: I'll keep this in mind as a test case.
mod6: ok, thanks, i've been working on a fix for a similar thing, actually, which is related to a similar test by ben_vulpes -- but haven't completed it yet.
mod6: so you ran something like `./v.pl p v foobar non-existing.vpatch` and then something ends up in foobar?
mod6: In regards to the above email section 0x04: To test this, one can simply grab polarbeard's vpatch and sig and drop them into place, then try to press the entire tree. This should hault throwing an error since the actual output hash does not match the ~expected~ output hash.
mod6: <+TomServo> I've finally got a node past the wedge, and there was much rejoicing << Rejoice!
mod6: the graph has been updated as well.
mod6: gl, let me know if anyone hits any snags.
mod6: ok mirror is updated. i've pulled, pressed, compiled and am now running with all the latest.
mod6: i'll also update the graph while im at it.
mod6: asciilifeform: ok cool thx.
mod6: yah, shinohai tested these for me today. seemed to work for him.
mod6: asciilifeform: any objections to me replacing those vpatches on the mirror now, or should I wait for you to give them a try first?
mod6: ermahgerd, gotta go blow some snow again.
mod6: put this in the cryptonomicon ^
mod6: yah, that's how my sigs look for v.pl: v.pl.mod6.sig
mod6: trinque: hmm. yah, i had to like use that tool, do a rescan and a restart, and then it was in there. but yea, that back port, if sane, would be best.
mod6: !up ascii_butugychag
mod6: (after importing privkey)
mod6: kewl. i seem to recall having to do a -rescan afterward but i could be wrong
mod6: !up ascii_butugychag
mod6: duh duh durr durrr durrr durr dur dur
mod6: trb logs === mailing list?
mod6: oh thought you meant #b-a
mod6: nearly 5 years now.
mod6: i read trb logs every day. who doesn't?
mod6: !up ascii_butugychag
mod6: !up ascii_butugychag
mod6: <+shinohai> o/ mod6 didja get some sleep ? << ah ya. no worries :]
mod6: then if all is good, i'll roll up another publication of the whole thing & call it v99995
mod6: (with some instructions etc)
mod6: I'll probably just send the patch to the ML to recruit people to help me test over the next two weeks.
mod6: in other news, ive got a patch for V that's not only the fix for the post-press hash checking, but also for the problem when running the graphing tool with a node that has no decendants. and a couple of small cleanup things.
mod6: i dunno either now, that was a giant pain in the ass.
mod6: well, hopefully my vtron works correctly.
mod6: are they not identical?
mod6: i guess that makes sense you wanted to see it that way - i thought the first way just because that way there ~is~ a diff to look at. but maybe this is better.
mod6: the left hand side is just the ~original~ patches + shiva
mod6: its only on the right hand side.
mod6: <+ascii_butugychag> the two trees, diffed. << i believe this is what I have and what you're looking for, is it not?