planck

Planck ClojureScript REPL
pyrmont 2020-04-18T08:15:29.023Z

@mfikes I wanted to try to fix #1029 but I can't get the test suite to pass. I've reverted to the current master and I keep getting an error at in the http-input-stream-test test. I thought the problem might have been that the URL that's checked is HTTP instead of HTTPS but it's not working no matter what I try—HTTPS, a different URL, nothing. Are you able to successful get the tests to pass?

pyrmont 2020-04-18T08:15:58.023500Z

This is the error message in the console:

FAIL in (http-input-stream-test) (file:44:173)
expected: (= 64328 (:file-size (io/file-attributes target-file)))
  actual: (not (= 64328 0))
./script/test: line 9: 527126 Killed                  script/test-unit

pyrmont 2020-04-18T08:20:37.024400Z

When I try to run <http://planck.io/copy|planck.io/copy> in the REPL, I get no errors but if I look at the temp file that it's supposedly reading the data into, it's empty.

pyrmont 2020-04-18T08:20:50.024600Z

Any ideas?

mfikes 2020-04-18T12:37:13.025Z

$ plk
ClojureScript 1.10.597
cljs.user=&gt; (require '[<http://planck.io|planck.io> :as io])
nil
cljs.user=&gt; (let [target-file (io/temp-file)]
       #_=&gt;     (io/copy (io/input-stream "<http://planck-repl.org/releases/andare/andare-0.2.0.jar>") target-file)
       #_=&gt;     (= 64328 (:file-size (io/file-attributes target-file))))
true

mfikes 2020-04-18T12:37:23.025300Z

@mike858 ^ working for me

pyrmont 2020-04-18T16:22:14.026300Z

Hmmm. Maybe something on the system I'm trying this on (it's the testing release of Debian). I'll try to build Planck from the most recent release of the source and see how I go.

pyrmont 2020-04-18T19:37:39.029200Z

Very strange. I don't get the error with the pre-built macOS version of Planck (v2.25.0) but I do get it when I build Planck from the v2.25.0 source on x86 Debian bullseye/testing (what will become v11). Given this version of Debian is pre-release, I don't know if it's worth much further exploration at this point. I might just submit the PR anyway and see how the automated testing goes.

mfikes 2020-04-18T19:39:04.029800Z

I think I may have seen similar things on some CI builds... something may be wrong somewhere.