log☇︎
197400+ entries in 0.71s
ben_vulpes: i think he's been around a while
jhvh1: BingoBoingo: tiny dancer :: "Tiny Dancer" is the name given to (and used when spoken about in public or otherwise) the 1/2 erection that can be grabbed at the base and twirled around, thus becoming a "tiny dancer." [ex:] "So who wants to go play frisbee?""I do, but wait until my Tiny Dancer goes away." [/ex] | 1.) A drink made with one part Stolichnaya Oranj, one part cranberry juice. Garnish with lime.2.) A (6 more messages)
BingoBoingo: !~ud tiny dancer
ben_vulpes: dd on bsd (os x, claims 1994 vintage) does not appear to pad
mircea_popescu: better than the tanning bed.
mircea_popescu: meanwhile at teh farm, http://68.media.tumblr.com/a0620361837d5fee98c28c530b5615d3/tumblr_on2gp6kV7M1w5g497o2_1280.png
mod6: so yah that's fucky
mod6: then tried `yes | dd iflag=fullblock of=out bs=1024k count=10` and says 10485760 bytes out
mod6: <+asciilifeform> yes | dd of=out bs=1024k count=10 << ya, tried this, 122880 bytes out
mod6: <+asciilifeform> mod6: can haz one moar plot -- just 300,000 and up, plox ? << i can do this easy enough, still want this?
doppler: oops, I actually do get that warning. totally didn't see it the first time. coreutils-8.27 here
jurov: on the yes test, i got warning:
asciilifeform: rather than having the reader lie to the operator.
mircea_popescu: do you want to get it ?
asciilifeform: put the padding in when and IF required -- on the end that requires it.
asciilifeform: if the iron wants it.
asciilifeform: let the WRITER pad.
mircea_popescu: not on their iron.
asciilifeform: could just the same do this without the padding.
mircea_popescu: if i have 3.5 blocks it allows me to read 4 blocks last of which is half 0s
asciilifeform: it inserts 0 silently in place of what failed to read.
asciilifeform: except that the idiocy in question doesn't preserve any data.
mircea_popescu: was a time when data was a lot more valuable, basically on account of the world not yet consisting of the www pressed shitboard. in that world of little valuable data, having any chunk "lost in the pipes" would have appeared typically soviet wasteful bureaucratism.
jurov: short reads prolly started as unix worse-is-better philosophy "api has these huge warts but as it can be easily fixed by retrying in userspace, it's okay"..posix only snowballed on
doppler: asciilifeform: POSIX sure seems to result in a lot of braindamage
trinque: folks that want a charitable interpretation of these might ponder a while re: who has the most time / resources to shitgnominate
doppler: I agree that -h should be the default in userland utilities
asciilifeform: if you omit the 'h', you get output in martian units
asciilifeform: ^ that one is at least plain to naked eye
shinohai: See the du -h retardation from previous thread
asciilifeform: doppler: once you figure out this puzzler, you will grasp what the thread was about
doppler: weird.. what's going on there?
Framedragger: ben_vulpes: of course i do. i meant, i see it here, too, and agree. but, yeah, 'tis a big problem
mircea_popescu: asciilifeform i betcha it's been in the old dog eared yellowed looseleaf notes the posix copied.
asciilifeform: mircea_popescu: ' i only implemented the standard ' has roughly same cachet as ' i was only following orders!11'
ben_vulpes: but you don't see that from your career of programmering to date?
a111: Logged on 2017-04-18 20:09 Framedragger: flabbergasted. may as well embrace tmsr's default malice interpretation here. because seriously.
mircea_popescu: http://btcbase.org/log/2017-04-18#1645740 << i can't iamgine how. the skeleton we found is just about 50 years old. ☝︎
Framedragger: i certainly see that, especially looking at gnu cat (omfg)
ben_vulpes: Framedragger: complexity is a the self-justifying disease of the programmer's mind
mircea_popescu: asciilifeform sadly, it IS the posix standard.
Framedragger: yes well, granted it doesn't support additional command line args, so has to handle fewer things. but then, maybe that, too, is *also* correct...
asciilifeform: ( spoiler : plan9's is the 'correct' one )
asciilifeform: ^ we had this on 2+ threads
trinque: cat thread is by now a yearly tradition
ben_vulpes: while we're doing these, i'd be much obliged if folks with a copy of drakma on hand would run `(drakma:http-request "https://untrusted-root.badssl.com")` and let me know what you get
Framedragger thought `dd` was one of those few 'no hidden bullshit, what you see is what you get' utilities from better times
Framedragger: flabbergasted. may as well embrace tmsr's default malice interpretation here. because seriously. ☟︎
Framedragger: apparently it's posix tradition didntyaknow
asciilifeform: why the FUCK would anyone specify 'count ATTEMPTS' rather than reads !
asciilifeform: Framedragger: picture if 'this util will format your hdd unless you supply the iflag=dontformatmyhdd option' buried somewhere deep in docs.
Framedragger: "Note if the input may return short reads as could be the case when reading from a pipe for example, ‘iflag=fullblock’ will ensure that ‘count=’ corresponds to complete input blocks rather than the traditional POSIX specified behavior of counting input read operations." OK
asciilifeform: Framedragger: almost like somebody thought about rng.
Framedragger: that's so *silent* and sneaky tho.
Framedragger: it's like the modern website. "i expect good bandwidth. you have low bandwidth? fuck yourself"
asciilifeform: but apparently doesn't like kB/s variable thing.
asciilifeform: mircea_popescu: e.g., dd, worx 100% of the time when copying multi-TB ssd, say.
Framedragger: mp is now like "i told ya so!!! tail!!!"
mircea_popescu: except for any time you try to use them, i find they are fine too! like one of those comedic toolboxes with a hammer that's seemingly attached except if you pick it up the metal falls off etc.
asciilifeform: mircea_popescu: apparently everything is 'fine' until you find the magic corner case.
mircea_popescu: asciilifeform i thought you thought core utils is fine.
Framedragger: why in the fuck would that be useful
asciilifeform: holy FUCK the sheer gangrene.
mod6: i'll try that next time i run a test.
asciilifeform: on what planet was this considered acceptable?!!!
asciilifeform: apparently, when reading slow or variable-speed source ( such as FUCKGOATS ) dd will sometimes fail to fill an entire block (default block size is 512 on most boxes) and PAD WITH MOTHERFUCKING ZEROS
mircea_popescu: or that.
mircea_popescu: as a general policy, when doing things of this nature (publishing intertesting stuff in forum) keep the whole echafaudage for day+ while people comment.
asciilifeform: of the worst sort, the 'folx in the know, know about it, and it will never be fixed'
mod6: ok, maybe might have to just another drive and drop 'em on there.
asciilifeform: i quite often refer to the raw blox.
asciilifeform: mod6: i recommend to keep'em around
mod6: i just deleted them this am
mod6: i gotta recut all the blocks anyway.
mircea_popescu: lettuce take a moment and make this one proper.
asciilifeform: anyway this is not essential.
mod6: im certain to screw that up
asciilifeform: then where the shutdown routine is, print it.
asciilifeform: and dbTotal += res ; say, after the print.
asciilifeform: so we find out total % of the node's bringup time spent waiting for bdb
mod6: how do i do that?
asciilifeform: (optional) make it print total odometers on shutdown
asciilifeform: one more thing
mod6: let me get that setup.
mod6: i'm up for a full re-eatblock. just want to make sure I'm not missing anything this time :]
mircea_popescu: would be useful to have the whole saga, and you're all set up for it, so should be easier than reconstructing the setup later.
mod6: so just add in this patch: http://therealbitcoin.org/ml/btc-dev/2017-February/000256.html ?
asciilifeform: also fwiw his total block delays (red) match the ones on my ssd node (zoolag)
asciilifeform: mircea_popescu: that's what mod6 was doing. except that he forgot the 'read' patch ^ and only had total and write.
mircea_popescu: nevermind the bunch of these, i want the whole eatblock'd blockchain.
mircea_popescu: can i has corresponding code snippet that was executing ?
asciilifeform: i posted a bunch of these.
asciilifeform: ProcessBlock (res == 1) took : 167839ms; db write wait: 130117ms; db read wait: 21201ms
mircea_popescu: no, i know. but look at the graph. so what ~exactly~ is this 'db write wait time' that is ~= the total ?
asciilifeform: thread is in the logs.
asciilifeform: there's exactly 1 segment that accounted for ~99% of time.
asciilifeform: mircea_popescu: i DID THIS
mircea_popescu: asciilifeform possibly time to re-do this whole eatblock instrumentation with a per-line timing profiler.
jhvh1: ben_vulpes: Trolling For Rainbow Trout In Still Waters - In-Fisherman: <http://www.in-fisherman.com/trout-salmon/rainbow-trout-steelhead/trolling-for-rainbow-trout-in-still-waters/>; Four Ways to Troll for Trout , Salmon, Crappies, Walleyes, and ...: <http://www.fieldandstream.com/articles/fishing/trout-fishing/where-fish-trout/2009/07/summer-trolling>; Trout Trolling Techniques - Game & Fish: (1 more message)
ben_vulpes: !~google trout trolling