a111: Logged on 2017-07-15 23:19 asciilifeform: and YES ben_vulpes your paster MUTILATES TABS
a111: Logged on 2017-07-15 10:36 mircea_popescu: why would any bad franchise get 26 sequels anyway.
trinque: sina: maybe read on a bit before "hurr durr loud bandwagon"
sina: trinque: I just came to try and get a rise out of asciilifeform :P
a111: Logged on 2017-07-15 22:47 asciilifeform: tomorrow will see how varies.
a111: Logged on 2017-07-15 22:52 mod6: yah, gotta be the version of my make is different than yours, plus, i'm not using adacore's gnat
a111: Logged on 2017-07-15 23:19 asciilifeform: and YES ben_vulpes your paster MUTILATES TABS
mod6: <+asciilifeform> !~later tell mod6
http://nosuchlabs.com/pub/fact.tar.gz << complete kit for above. sha512==26198604bff50d3411e343a30b97f4babe3a6b291fca267435cecd6a5438a08862b550198a49dd5549dda00c841d95afc1443f597587710b83c7fa65effa9c73 << alright thanks!
mod6: I'll check into wtf is going on. I'm running gnat on 4.9.2 on deb.
mod6: im probably condemmed to going through all the hoops to get gnat setup on gentoo. i just haven't ventured into it yes as it seems like a pretty timely, process.
mod6: im gonna try to see if I can resolve the issues. probably just my environment or whateve.r
phf: it does seem to mangle ~something~
phf: $ dd if=/dev/random of=foo bs=1024 count=100
phf: 82a2e85430ce36b759c5422a7433001d6e64b777 foo
phf: $ curl --silent $(cat foo|wotpaste)|shasum
phf: 42a67f70e3128dba8978def6e03ba9577f11dad0 -
phf: oh i think it transcodes
mircea_popescu: send it as postdata or what was it, special binary format
phf: yeah, wotpaste does the pasting, curl then pulls it back. i wonder if curl download negotiates it up to unicode
phf: since i'm posting to a form though, it must be rfc 2388 compliant. afaiu posting raw binary data wouldn't work, because server needs to know which field the data is associated with
phf: do you have a full command with --data-binary that you're using to upload?
phf: it's not, --data-binary takes <data> as an argument, at least according to man
mircea_popescu: (nfi why we're even testing uploading binary to wotpaste, as that's not what it's for, but w/e.)
phf: i checked them, they look correct
mircea_popescu: because i see 00000000: 0001 0203 0405 0607 0809 0a0b 0c0d 0e0f ................ as first line
mircea_popescu: oh wait, you post the first one and get back the 2nd one ?
phf: sorry, the two are not actual files, but hexdumps of the files i'm trying to post/getting back
mircea_popescu: try repolacing -F 'pastebox=@-' \ with --data-binary 'pastebox=@-'
mircea_popescu: try repolacing -F 'pastebox=@-' \ with --data-binary -F 'pastebox=@-' \
phf: no, because --data-binary takes an argument
mircea_popescu: phf it does, the actual stuff you're sending. i imagine you feed it to curl via something somewhere in the call yes ?
mircea_popescu: no idea why i'm taking partial code/functions and making assumptions. here :
sina: hey phf, quick q, is lisp memory safe?
phf: common lisp specification defines a memory safe language, yes, but in the crevices of "undefined behavior" you can have memory related exceptions. for example you can define a function with (safety 0) optimization declaration, which will neglect to check the type of a passed argument, which might (and often will) result in a memory exception.
sina: that sounds reasonable
mircea_popescu: put your test lines in the first file ; examine the results.txt file for the results.
trinque: diff <(curl -s $(cat foo | wotpaste)) foo Binary files /proc/self/fd/11 and foo differ << with his wotpaste func and foo
mircea_popescu: phf what i mean is, im stuck guessing how wotpaste() { is called and etcetera.
phf: i say it right there! "cat foo | wotpaste"
trinque: seems sorta like there's a double encode happening.
☟︎ sina: double encoding is the best and least confusing kind of encoding
sina: alright ladies and gentlemen, off to visit some friends and have some pho
sina: enjoy your remaining weekend!
ben_vulpes: thanks for the debugging input phf, mircea_popescu
ben_vulpes: i'm very recently hamstrung in degrees of freedom by hardware failures, so i won't be terribly responsive for the immediate future. working on it tho.
a111: Logged on 2017-07-16 03:22 trinque: seems sorta like there's a double encode happening.
mircea_popescu: BingoBoingo usg.pinoy moved on to whining about imminent usg defeat ?
BingoBoingo: mircea_popescu: Hard to tell if usg.pinoy or PRC.Chinoy
mircea_popescu: asciilifeform best i can tell, wotpaste simply drops nonascii chars. was something in the makefile not ascii ?
trinque: spent more time freaking out than producing a diff would've taken.
trinque: seems it wasn't the tabs; those came back
mircea_popescu: trinque i am actually running a terst and it's pretty mindboggling.
trinque: I think echo adds a newline, for one
trinque: just... does. and look, they gave ya a "echo -n" to undo it! choice
mircea_popescu: (i don't expect it does, because look in 2nd paste. the -=== bit is produced by echo.
trinque: -n do not output the trailing newline
mircea_popescu very much recommends this test : pick random textfile, put it through the above code, see if you find a dismatching line.
mircea_popescu: atm watching it scroll, however many 100s of lines in, they all match.
trinque: phf's "foo" breaks it, though really, if the thing's an ascii paster, I dunno that the bug's anything but "fed uniturds, did not tell user to fuck off"
mircea_popescu: pretty sure it simply drops non-ascii chars silently. which is the right thing at that.
☟︎ mircea_popescu: anyway, i'm calling it good before i fill the guy;'s disk with random lines.
jhvh1: BingoBoingo: Bitstamp BTCUSD last: 1990.18, vol: 19107.72677751 | BTC-E BTCUSD last: 1980.001, vol: 7272.76637 | Bitfinex BTCUSD last: 1992.9, vol: 40170.85769058 | BTCChina BTCUSD last: 2073.623544, vol: 13827.40170000 | Kraken BTCUSD last: 1971.542, vol: 12007.1922058 | Volume-weighted last average: 2000.62804597
phf: ben_vulpes: are you using hunchentoot?
phf: so it shouldn't be loosing anything in 0-127 range, at least the foo file comes through clean. it is trying to parse the input as unicode (and i'm pretty sure it's the server doing it, because curl is sending it 8bit clean)
phf: because everything >127 is getting replaced with efbfbd which is unicode "REPLACEMENT CHARACTER" in utf-8
mircea_popescu: phf yes but does it ever collate into an unicode character or anything of the sort ?
phf: foo is a specially crafted file which is simply a sequence of bytes from 0 to 255
mircea_popescu: possibly there's something else afot though, because that wouldn't have afected a makefile, ie the original problem is it.
phf: right, we're in agreement here. ascii should've remained untouched
phf: i mean, we've had very many tests demonstrating it, part of ongoing "paster ate my characters" asciilifeform saga
phf: but i figure i'll try pushing a binary file through (which wasn't the spec anyway, just wanted to see what actually happens)
mircea_popescu: fwiw i never did manage to verify the saga was anything more than alf's extremely short fuse.
mircea_popescu: and i am not about to see 500 or 5 million instances of that morph into some kind of actual proof of anything.
phf: nor would my explorations ever corroborate that
mircea_popescu: anyway, so far : it's not clear that it actually does anything untoward to ascii ; my tests as they were failed to find an example. we did discover it replaces nonascii chars with some random gunk, which yes should be changed but not really much of a point or anything
mircea_popescu: i thought maybe it is the case that it takes a 2 or 3 byte item which starts with valid ascii and tries to interpret it as some sort of unicode bs and in the process ends up applying a transform to the text somehow. but unless we have the actual magic string, we're not finding this.
mircea_popescu: i tried for isntance feeding the original makefile in line by line with my comparer thing, but all the lines match.
phf: so the utf-8 parser takes anything in the 0-127 range as is, so we definitely wouldn't have any "magic string" cases in the happy path (the unhappy path being that you can apparently specify file type and encoding when posting to an rfc2388 form, and the server can happily decide to transcode it in whatever way it pleases)
mircea_popescu: there's no way he's fixcing that however, outside of making a whole new tmsr
http deedbot: aerial voiced for 30 minutes.
Framedragger: i'll do the latter, as to the former, i'm afraid it doesn't have it as of yet
mircea_popescu: Framedragger imagine you know, five years from now the situation repeats. except then there's no tardstalk anymore. but it's ok, we have the archive link. o look, it's just a dangling link.
Framedragger: i just wasn't sure if you were looking for a particular downloaded-from-earlier copy of that zip file
mircea_popescu: instead of that sad fate, pile them into monthl;y tarballs, deed the previous month's tarball each time a new month starts and lo! major piece of infrastructure.
Framedragger: (i thought you maybe wanted to check if archive.is tampered with it; which yes we should be able to do as well)
mircea_popescu: Framedragger above described mechanism will do that for free, yeah, just gotta have to care enough to put a link in log.
jhvh1: shinohai: Bitstamp BTCUSD last: 1932.04, vol: 23428.84569111 | BTC-E BTCUSD last: 1955.58, vol: 10221.57286 | Bitfinex BTCUSD last: 1919.7, vol: 49221.3374292 | BTCChina BTCUSD last: 2002.933476, vol: 12473.25150000 | Kraken BTCUSD last: 1923.25, vol: 13245.4099681 | Volume-weighted last average: 1935.73341543
BingoBoingo: OMG Costa Rica has warehouse churches too!!!
BingoBoingo was a bit disappointed, this was merely traditional church building kept as warehouse. Was expecting USian phenomenon where new construction church is actually build in the manner of a warehouse. Corrugated steel and all.
☟︎ a111: Logged on 2017-07-15 23:16 asciilifeform: !~later tell mod6
http://nosuchlabs.com/pub/fact.tar.gz << complete kit for above. sha512==26198604bff50d3411e343a30b97f4babe3a6b291fca267435cecd6a5438a08862b550198a49dd5549dda00c841d95afc1443f597587710b83c7fa65effa9c73
phf: asciilifeform: just fyi, your package of goodies compiles, i haven't ran it through, but with gdb i can catch it mostly doing Mul, and producing sensible states
a111: Logged on 2017-07-16 19:49 BingoBoingo was a bit disappointed, this was merely traditional church building kept as warehouse. Was expecting USian phenomenon where new construction church is actually build in the manner of a warehouse. Corrugated steel and all.
deedbot: mimisbrunnr voiced for 30 minutes.
deedbot: candi_lustt voiced for 30 minutes.
phf: !W (DEFUN FACTORIAL (N &OPTIONAL (ACC 1)) (IF (<= N 1) ACC (FACTORIAL (- N 1) (* ACC N))))
phf: !W (= *ref* (factorial 65536))
BingoBoingo: <mircea_popescu> BingoBoingo no, that's precisely what it was. << Ah
phf: it's few lines above, parse-integer'd fact_out.txt
a111: Logged on 2017-07-15 13:00 asciilifeform: btw if you're actually doing something that doesn't need constanttime, you can simply put the obvious check-for-zero in the karatsuba and get 2-9000x boost for mul.
phf: parse-integer actually took significantly longer than factorial (i'm trying to figure out how to get a millisecond timer out of sbcl to wrap factorial to answer your question, but i don't think there's anything native)
phf: !W (let ((t0 (get-internal-run-time))) (factorial 65536) (float (/ (- (get-internal-run-time) t0) internal-time-units-per-second)))
deedbot: what voiced for 30 minutes.
deedbot: whatisthis voiced for 30 minutes.
BingoBoingo: whatisthis: Who is your daddy and what does he do?
whatisthis: im reading the trilema site. and I don't really understand what's going on. But I'm terribly intrigued to continue reading it
a111: Logged on 2017-07-16 06:02 mircea_popescu: pretty sure it simply drops non-ascii chars silently. which is the right thing at that.
whatisthis: yes. sell all of my stuff and contribute to TMSR however I can?
BingoBoingo: <whatisthis> yes. sell all of my stuff and contribute to TMSR however I can? << No, first tell up who your daddy is and what does he do
phf: whatisthis: trilema is some guy's personal blog. it kind of should be obvious from the format of things. typically when one discovers something, one should spend some time circling it, this way and that, trying to figure out its nature. you will gain very little by coming on "hey guyz! whacha doing here!!"
phf: it's a barn raising! you in? and then we'll have us a good ol' lynching!
mod6: <+asciilifeform> results of torture test: << thanks for posting your results.
mod6: I'll be spending some time this week to try to get adacore's stuff built into gentoo with gcc. not sure now how this will go, but will let you guys know.
mod6: perhaps if i can get that working, then I can use the -cflags -O2 thing alright without issues.
BingoBoingo: <asciilifeform> nah everybody knows, first lynching, then barnraising << AHA, barn commemorates honored tree!
phf: "why would we use it to scan what you're asking us to scan, if we can just go and get the original, lulz"
BingoBoingo wonders if we have moved on yet from Axe Time, Sword Time on to Wind Time, Wolf Time