Fork me on GitHub
Petrus Theron11:03:42

Probably a conditional reader macro that Parinfer moved around. Why won't it tell me which file this occurred in? I could solve the problem instantly if I knew where it was


Well, looking at it's somewhere in your :require s .. as to why there's no try/catch or logging there, well, I guess no-one bumped up against it yet or deemed it wasn't common enough to add it. Let me know what caused it if you do find the problem!

Petrus Theron12:03:24

Managed to debug it by commenting out every require in my main app.cljs file. Then I turned on cljs compile with watch and manually added each line back one at a time until I found the error. The problem was a require from a cljc file that was commented out, so I suspect it didn't say "no such namespace" because the file existed, but I'm not sure. I just wish it would tell me the name of the text that it says isn't a symbol, because it's fast to debug in that case.


Having some trouble with task options of type [str]. Get an exception every time I provide it: e.g.

(deftask foo
  [x blah BLAH [str] ""]
  (prn blah))
running boot foo -x bar gives:      745
java.util.concurrent.ThreadPoolExecutor$  617
 java.util.concurrent.ThreadPoolExecutor.runWorker 1142
               clojure.core/binding-conveyor-fn/fn                 core.clj: 2022
                                 boot.core/boot/fn                 core.clj: 1032
                         boot.core/construct-tasks                 core.clj:  994
                                clojure.core/apply                 core.clj:  657
                boot.user$eval836$fn__837.doInvoke                         :   85
java.lang.IllegalArgumentException: option :blah must be of type [str]
        clojure.lang.ExceptionInfo: option :blah must be of type [str]


Is this broken, or am I just not using it correctly?


That works for me

(! 595)-> boot foo -x bar

Tue Mar 13 12:42:29
(! 596)-> cat build.boot 
(deftask foo
  [x blah BLAH [str] ""]
  (prn blah))
(but tasks should return functions, in general)


Looking at that error, I think maybe you're trying to invoke the foo task elsewhere in your build.boot @lsnape?


@seancorfield no other tasks named foo. I first saw the problem with boot-new -a which also takes [str]. Think it might be to do with the boot version.


@lsnape I'm on 2.7.2 -- what are you using?


@seancorfield ah yes 2.7.2 works. I was unknowingly running 2.8.0-SNAPSHOT.


Interesting... I'm surprised there would be a breakage moving up to that!


FWIW, when I run with 2.8.0-SNAPSHOT, it still works

(! 605)-> BOOT_VERSION=2.8.0-SNAPSHOT boot foo -x bar

Tue Mar 13 15:00:10
(! 606)-> cat build.boot 
(deftask foo
  [x blah BLAH [str] ""]
  (prn blah))


(and that does run the latest snapshot version as of today)