13900+ entries in 0.023s
mod6: something like that. does this make sense?
mod6: so if your block index goes from 385,000 to 408,000, you could tell it "407,000" and then the output would contain everything from 385,000 to 407,000
mod6: but it'd be a much better tool to just produce a new file with all blocks in the original previous to block n.
mod6: you could just ditch the entire latest one (numerically)
mod6: s/in the future/after adding a feature/
mod6: i may try to find some time yet this weekend to take a look at this blkcut thing -- this may be away to roll life saving numbers on your block chain after a power outage in the future.
☟︎ mod6: i think others have had problems with the same exact thing. power goes out -> bad things may happen.
mod6: thestringpuller: anyway, i get that you're "pissed" as you said the other day. if this is production server, you need to have some sort of backups indeed imo. if this is development, well, it's all part of the fun.
mod6: maybe that'd fix his problem.
mod6: ok. cool. yeah, was thinking it'd be cool if we could get his blockchain height, say 408,001 and then chop off the last say, 1000 blocks so he'd be starting at 407,001
mod6: im got my hands full. am asking for thestringpuller who seems to be struggling
mod6: well, im kinda trying to .. lol in a short cut way (without having to try to actually use it)
mod6: asciilifeform: hey (i think I've asked this before) but; the blkcut utility doesn't allow a guy to exacto-knife one block out of a blkindex file does it?
mod6: or did you see others?
mod6: and yah, as far as I can tell asciilifeform, the only #b-a links there (three of them) are pointing at wiki.bitcoin-assets.com
☟︎ mod6: is this stuff ready?
mod6: the content is baked, not sure about the infrastructure/container itself.
mod6: i haven't updated the links because i wasn't sure that the deedbot wiki page is fully baked yet.
mod6: <asciilifeform>
http://thebitcoin.foundation still contains a buncha #b-a links ? << yeah, shinohai did a project where he transfered over the stuff there like the wiki to the deedbot page.
mod6: not sure. was this the same blockchain that you've been using with this same build? that error you recieved makes me think something got munged.
mod6: if you use the script referenced above, it'll verbosely print out the patches being applied. which you can log into a file.
mod6: follow the steps in that log link.
mod6: i would try building with the latest and see.
mod6: any particular reason?
mod6: since your version shows 50400, it makes me inclined to think that you have some downlevel version since it should say 99999 if you have the latest.
mod6: that'll tell me what is in your patches dir, but not necessarily what you actually built. you haven't said yet what you built or how.
mod6: do you have the cutblock code in your build?
mod6: mine is happily running along past that block. mine is fully caught up.
mod6: not sure what else might be the problem there though.
mod6: thestringpuller: so, one thing i can tell for sure from your dpaste is that you're not running the latest trb tree.
mod6: this is a temporary fix, and it's still on the agenda to get this resolved so we don't rely on remotely pulling down deps. stay tuned.
mod6: everything else stays the same.
mod6: Gentlemen, I must bid you Good Evening. I'll pick this back up with you on the 'morrow. :]
mod6: i think both are reasonable. this should be tabled for now for thought-experiment and real-experiment time.
mod6: instead of mod6_v.vpatch or something
mod6: i think that it makes it confusing if we call it 'v-genesis'
mod6: in way that asciilifeform lays it out, in the sense that this vpatch would start from 'false' and end on 'SOME_HASH' and create a file(s)|directory(ies) that did not previously exist, then yes a 'genesis' but only on concept - not in name. as we shouldn't not confuse the two imho.
mod6: so maybe, everyone's call, including yours for a 'v-genesis' vpatch had me thrown that it should be a 'genesis' and not a simple vpatch to what currently already exists out there.
mod6: that's all i was trying to say :]
mod6: don't worry about that. paint me a picture on how you might go about the task - how and where does t.pl go? or v.pl ?
mod6: this would sit adjacent to the 'bitcoin' directory? (just trying to get a visual in my head here)
mod6: so what would your implementation look like here? a patch to a current leaf of the trb patches that inflates say t/t.pl from 'false' on the end of the trb 'light-code' ?
mod6: so we either have ~one~ universe, or there is >1
mod6: don't add nsa's key to your wot, and you wont see that patch right?
mod6: so we are agreed then that things outside of the trb light-cone, get its own light-cone - a multiverse of things, yeah?
mod6: where should this vpatch live?
mod6: let's say that i have this project called `t'. and I'd like to make it readily availble and a genesis for this specific tool.
mod6: let's paint a picture.
mod6: im fine with this too -- alf sees this as a mistake. so just thought I'd take a minute to address the alternative. unless there is something that I haven't considered? asciilifeform? suggestions?
mod6: just trying to address alf's messages.
mod6: mircea_popescu: well, i think it's a better, cleaner practice.
mod6: one inflates the trb universe into bitcoin, the other into v. i guess it doesn't have to be that way.. v-genesis could be added later on down the line as a leaf node. but then it probably shouldn't be named "genesis" as that seems to break the convention.
mod6: these are multiple roots.
mod6: and in this case, some of these things are somewhat related, and that might be ok. but in the future, there might be things that are not so closely related. so might be trying to get out in front and make this able to handle multiple projects by seperating them out.
mod6: so i kinda see this in two ways. either i place v/t/whatever into /v/ and we have many multiple roots, inwhich case when you pull from the mirror you end up with the following dirs: bitcoin, t, v, whatever, ... or we can break this up into multiple projects.
mod6: arg. what a long day. can't believe it's already the thirteenth
mod6: <+mircea_popescu> you can't say lisp without S! << heheh. "lithp"
mod6: ah cool, my graph did turn out right. lol. "i can use my own thing!"
mod6: omg we've got projects and verk
mod6: %a t F "Add Long Notes Feature" "Implement functionality so that users of T can create notes longer than 300 chars if necessary."
mod6: %e t 1 S "Update tb0t with Long Notes" "After the implementation of the Long Notes feature, roll out new version of tb0t." 2
mod6: %e t 1 S "Update tb0t with Long Notes" "After the implementation of the Long Notes feature, roll out new version of tb0t." 1
mod6: %a t S "Update tb0t with Long Notes" "After the implementation of the Long Notes feature, roll out new version of tb0t."
mod6: anyway, the good news is; its not chiseled into stone.
mod6: we'll see if i did that all backwards lol.
mod6: %e v 3 T "Update Tests" "Update V cucumber tests for 99994 with specific testing around separate projects." 4
mod6: %e v 2 X "Update V Documentation" "Update V documentation for 99994 release." 4
mod6: %e v 1 S "Release V 99994" "Publish new version of V [99994]." 2,3
mod6: %a v T "Publish V-Genesis" "Publish V-Genesis post 99994 release." 1
mod6: %a v T "Update V" "Implement ability for V to pull separate projects from the mirror based on hash (or possible alias)."
mod6: %a v T "Update Tests" "Update V cucumber tests for 99994 with specific testing around separate projects."
mod6: %a v X "Update V Documentation" "Update V documentation for 99994 release."
mod6: %a v S "Release V 99994" "Publish new version of V [99994]."
mod6: cause that's really what we care about.
mod6: yeah, i'll have to work out something with that. i think on the server side, the hash value as dir name is a nice touch
mod6: but sure, makes some sense.