lumo 2018-02-09

I am compiling canary (`1.9.1024`) locally and spotted a potential problem:

failed compiling file:out/cljs/spec/alpha.cljs
	 (new)
	 Function.cljs.core.ex_info.cljs$core$IFn$_invoke$arity$3 (NO_SOURCE_FILE <embedded>:2058:72)
	 (lumo/compiler.cljs:644:25)
	 Function.lumo.compiler.compile_file.cljs$core$IFn$_invoke$arity$3 (lumo/compiler.cljs:655:4)
	 (Object.lumo$closure$compile-file)
	 (lumo/closure.cljs:1644:21)
	 (Object.lumo$closure$-compile)
	 (Object.lumo$closure$compile-from-jar)
	 (lumo/closure.cljs:1679:21)
	 (Object.lumo$closure$-compile)

Cannot write 
	 Object.com.cognitect.transit.impl.writer.marshal (NO_SOURCE_FILE <embedded>:6019:288)
	 Object.com.cognitect.transit.impl.writer.emitObjects (NO_SOURCE_FILE <embedded>:6006:181)
	 Object.com.cognitect.transit.impl.writer.emitArray (NO_SOURCE_FILE <embedded>:6006:407)
	 Object.com.cognitect.transit.impl.writer.marshal (NO_SOURCE_FILE <embedded>:6019:58)
	 (NO_SOURCE_FILE <embedded>:6012:409)
	 cljs.core.PersistentHashMap.forEach (NO_SOURCE_FILE <embedded>:1502:182)
	 Object.com.cognitect.transit.impl.writer.emitMap (NO_SOURCE_FILE <embedded>:6012:286)
	 Object.com.cognitect.transit.impl.writer.marshal (NO_SOURCE_FILE <embedded>:6019:129)
	 Object.com.cognitect.transit.impl.writer.marshalTop (NO_SOURCE_FILE <embedded>:6021:120)
	 com.cognitect.transit.impl.writer.Writer.write (NO_SOURCE_FILE <embedded>:6022:390)

@richiardiandrea file an issue with a repro please

I am compiling with latest master and I actually have that error when I boot release

The step that fails is the aot of macros and I am building cljs with script/build. Maybe I need some additional step to produce cljs's artifact

@richiardiandrea just a sniff test, sometimes if I change dep versions and I have cached js artifacts, the first errors I see are strange transit errors - I have no idea what’s actually going on there though

@noisesmith thanks I am trying a couple of things but your suggestion might be what is going on there

it would be interesting to find out why it’s always transit that acts up if there’s bad cache

and I would expect the reading operation to fail, not the write, anyways...maybe there is something else going on