2000+ entries in 0.245s
mircea_popescu: it's not exactly a common condition, this ; which is both why i said something and why it wasn't noticed. simply no
test for ~this~ never seen before nonsense
trinque: miner wants the chicks, yet I'm supposed to STD
test them for him
trinque: eh the
test.
test.local was just me leaving turds in /etc/hosts
mod6: yeah, good call. should be easy enough to drop em in and
test 'em.
shinohai: Not bad here, you? Hopefully I can get time this afternoon to add asciilifeform 's newest goodies and
test mircea_popescu: girls engage in this sort of fatty grooming as a shit
test. if you agree with her that her fat friend also deserves "a life" aka someone to pay for her children, perhaps you should.
shinohai: ty asciilifeform .... will
test this afternoon
shinohai: Lots of irons in fires atm, but exciting development asciilifeform .... I will
test in < 24 hrs
hanbot:
test tx via trb using sendtoaddress fails to send diddly squat, meanwhile @ blockchain.info: transaction rejected by our node. Reason:Script resulted in a non-true stack: []
trinque: I'm going to aim the deeds service at #trilema-trinque for a few minutes to
test.
mod6: my
test node gets bh'd all the time, still responds to rpc commands. i typically do the samething, stop. wait a bit, restart.
phf:
http://btcbase.org/log/2017-02-10#1612714 << is handy, but i can't bring myself to replacing safety critical ssh with it. i've had plenty of opportunity to
test it though, and it's best option for when you're trying to connect to server over a public wifi running over cell network off a generator
☝︎ shinohai: It isn't bad really. You can
test drive in a chroot until you have time to build actual kernel.
a111: Logged on 2017-01-30 19:05 asciilifeform bought a set, will
test and post result.
Framedragger: yes, *some*. but not enough automation, apparently; and not enough falsification in this case, as is very much apparent :/ should have been an obvious catch by either automated
test or at least manual
test. was (very shamefully) a wee bit too lazy with this last command.
mircea_popescu: the
test MAY NOT BE > 0 (or -1 ?) and < 0x10000000000000000. if the compiler does that the compiler is very, very stupid.
mircea_popescu: the range is 0 to 0xfffffffffffffff. the
test is >= 0 and <= 0xfffffffffffffff.
mircea_popescu: asciilifeform ah, no, i did
test it. the converter is cheap, which means cheap. low q optics.
Reuel: Ignore my
test, also, have you guys automated the login process with the OTP etc?
diana_coman: as to the trouble there: it's more than a concern - it invalidates your "
test"
diana_coman: Reuel, let me see if I get this straight: you want to implement a "small" scale model of democracy in order to
test whether it works; at the same time, you propose to implement it on a model of reality that is purposefully broken because..."scope is too small for it to matter"?
phf: the whole point of "no child left" is to skew literacy rates through standardized multiple choice. "by the end of this course you will recognize the words dog, cat and food. this will also be in the
test"
mod6: You see, when I've tested this in a single edge graph system -- a simple
test vpatch set, this problem doesn't occur. a->b->c->d->e, remove 'c', and you just have a->b -- my current implemntation does this fine.
mod6: I've created some new tests and all of which have been looking good. But then I noticed what seems like a problem on the last, new
test, to implement. In fact, it was the last step of the last new
test.
mod6: i actually kinda wanna
test this guy out
pete_dushenski: in other news, "In this article World Bank poverty estimates are used to systematically
test the relationship between changes in poverty and exogenous changes in real domestic food prices. We uncover indicative evidence that increases in food prices are associated with reductions in poverty, not increases."
mircea_popescu: and on the other hand, "the number four told me to headbutt a door!". really, it did ? i suppose, perhaps, if the number four is followed by a double-sifr and occurs on your blood
test result sheet right where the locals wrote "glucemia" it may be said "the number four told me to stop eating icecream", but it is rather forcing the point.
Framedragger:
http://btcbase.org/log/2016-12-31#1594781 << hmm. what i could do is, check that all generated gpg keys have the right e and N (by comparing to the e,N,IP CSVs that i fully trust); to make sure that i didn't mess up the gpg-generation thing. i don't think it'd be really possible, and i had done some manual checks before, but maybe worth to write an automated full-on
test.
☝︎ mod6: Update: Cleanup, and construction of new automated tests to provide functional
test coverage for V-99994 is now underway.
mod6: <+davout> mod6: i think it would actually be the least painful part to
test << anyway, i hope so. im sure there will be more discussion in coming months.
ben_vulpes: mod6: "
test[ing] this" is actually how i got on the alpha centauri miner quest
davout: mod6: i think it would actually be the least painful part to
test mod6: and am going to try to build tools, if needed, to help
test this.
ben_vulpes: what's an insane input that breaks the shortest common substring
test?
ben_vulpes: would a smallest common substring
test suffice here?
ben_vulpes: if you don't bottom it out it's not a proper
test drive
mircea_popescu: moreover, it's a fine lithmus
test : doesn't know of phuctor by now, isn't actually involved.
a111: Logged on 2016-12-28 01:58 phf: also as a rule you don't really want to let string output streams escape their scope. they don't have standard type (one cmucl it's lisp::string-output-stream for example), so you can't
test for it, and for all intents and purposes they act as incomplete builders: you can't do anything with them except get their value, so why not get value there and then?
phf: also as a rule you don't really want to let string output streams escape their scope. they don't have standard type (one cmucl it's lisp::string-output-stream for example), so you can't
test for it, and for all intents and purposes they act as incomplete builders: you can't do anything with them except get their value, so why not get value there and then?
☟︎ mod6: and when I do that above
test ^, i never hit this line: death("Cyclic Graph!\n");
mod6: im not sure if i follow. are you saying that genesis isn't a good place to
test it because it is a root?
mod6: asciilifeform: hey, say I wanted to
test my toposort...
mod6: yah, so, in this: a->b->c->d ; I basically just got rid of 'c', and then tried to press a->b->d (all signed by x) and it does fail. was this what we were trying to achieve? If not, i'll do another
test np.
mod6: mircea_popescu: this is a solid point for testing, let me give this a
test and see how it goes. will report.
trinque: ben_vulpes: wooo! I'll
test that soon as I have coffee in hand.
mod6: i think it's fine. you make a testkey, you sign your
test vpatches, you press &
test, etc. then we're using encryption everywhere. and we fail fast.
mod6: <+mircea_popescu> there shouldn't be any flag - nor should it press unsigned things. && <+mircea_popescu> with the
test key ? why not ? fucks with your workflow ?
trinque: why have that code path present at all? fix patch, apply
test patches by hand
mircea_popescu: with the
test key ? why not ? fucks with your workflow ?
mod6: I don't think it is reasonable to sign every thing I want to
test.
mircea_popescu: better off making a
test key and adding it to seals than this