: I'll get around to it later today and will let you know how it went.
: bvt: the antecedents/descendants commands behave as expected now indeed; the output from vtree though seems confusing as it is now because of the order in which children are apparently shown in between siblings so that one has to track and count spaces to be able to say what belongs where and what seems the child of the node immediately above turns out to be meant instead of child of node 2 lines above, not sure if you intended it like ...
: ... that; for illustration, here's the output
from vtree and antecedents on eucrypt_oaep_fix_checks.vpatch (ran in the same test dir that can be had from here
); antecedents gives the correct path genesis->ch6->ch7->ch9->ch10->oaep_fix_checks, but in vtree's output it's very hard to tell that ch10 is meant as child of ch9 rather than ...
: bvt: also, mind packing in next vpatch either removal of that Makefile or an update to it so it covers the new .gpr files? As it is now it's doing half a job and even that unclear why via makefile anyway - it would possibly make more sense to just have one .gpr file that allows you to build all with a single command but anyways.
: mp_en_viaje: do you have a specific goal in mind for Thursday's wallet work? Do you also want to use the online part (I would imagine so but could technically be done without)? If so, note that it takes about a day to scan the present blockchain once fed the address(es) of interest, and requires a TRB node. If you wish to also send the rawtx using it, as would be most proper, we'll also need that
: polarbeard patch which I haven't yet got reground.
: mp_en_viaje: In preparation of our next attempt at getting this project done, I've been going through my faff-fest
from last time.. and trying to figure out how we should pick back up
: Logged on 2019-12-04 04:37:32 mircea_popescu: lobbes wtf dude, you set ALL of these to 2019-12-03 22:03:06 time ?! didn't we go through an entire discussion of how it should increase monotonically ? gah.
: Then I realized that all that insanity was indeed because I was needlessly translating all kinds of strings across boundaries. I think the cleanest way to do this historical (May 28, 2016 to Now) log backfill is if I just provide you a text file in the same format as your "logstory.txt" you reference in this comment
: Since you already have that script working, I figure we may as well use it for this piece. All my log history is in a Postgres database though, so I need to "convert" my data at least once. Would you be able to send me a sample of that logstory.txt?
: Also, are you good for tomorrow night or were you looking for doing this during the day? I'm slaving in the mines tomorrow but my night is clear. If need be I may be able to weasel a work-from-home day though, so I'll check back when I wake up tomorrow