@thheller I’m wondering what might be going with the compilation time of my project. Here’s the case. I’m using reagent with semantic-ui-react. Just requiring (not using) the file containing the wrapped semantic-ui-components (all defonces) at least triples the compilation time for the first as well as subsequent compilations. I can see that the file count is going up but I hope that wouldn’t slow it down so much. Could you shed some light?

[:app] Compiling ...
[:app] Build completed. (207 files, 1 compiled, 0 warnings, 0.46s)
[:app] Compiling ...
[:app] Build completed. (911 files, 1 compiled, 0 warnings, 1.82s)
[:app] Compiling ...
[:app] Build completed. (911 files, 1 compiled, 0 warnings, 2.27s)
[:app] Compiling ...
[:app] Build completed. (911 files, 1 compiled, 0 warnings, 1.67s)

@denik compile with --verbose or :verbose true in your config. should make it clearer.

might be that the writing to disk part is actually the slow part since 700 extra files needs to be written

Will do. @thheller since the files don’t change can they not be rewritten?

Hi thheller, is there posible to create multiple :node-test builds? My shadow-cljs.edn:

{:deps {:aliases [:dev :test]}
 :cache-root ".shadow-cljs"
 :builds {:main {:target :npm-module
                 :output-dir "lib"
                 :compiler-options {:source-map true}}
          :main-test {:target :node-test
                      :output-to "lib/main-test.js"
                      :autorun true
                      :compiler-options {:source-map true}}
          :delay-test {:target :node-test
                       :output-to "lib/delay-test.js"
                       :ns-regexp "-test-delay$"
                       :compiler-options {:source-map true}}}}

@bolasblack sure, no problem.

I got a warning:

[:main-test] Build completed. (72 files, 0 compiled, 0 warnings, 6.19s)
[:main] Build completed. (174 files, 1 compiled, 0 warnings, 6.25s)
[:delay-test] Compiling ...
[:delay-test] Build failure:
The required namespace "utils.airtable-test-delay" is not available.

do you include that somewhere?

No

odd

ah is the file named incorrectly perhaps?

with - instead of _?

😂😂😂😂 oh sorry

I forgot rename the file

It's so embarrassing 😣 😂

not really. I would make this mistake constantly if Cursive wouldn't warn me about it.

there should probably be a better error for this. you shouldn't have to guess whats wrong. it should tell you.

Thanks for your comfort:laughing:, if the error be better, I think it will save lots my life (I make this mistake many times)

@denik I did some tests and it appears the resolve performance is terrible with so many files. didn't optimize any of that since I didn't expect an issue with it. I'll see if I can tweak that a bit. https://github.com/thheller/shadow-cljs/issues/235

any ideas?

very odd. is maven or clojars blocked maybe?

yeah - weird, I’ll check

I’m using an AWS CodeBuild CI image

I don’t have lein installed but I don’t think Shadow needs that - yes?

not required yes

the error is from here https://github.com/thheller/shadow-cljs/blob/master/packages/shadow-cljs-jar/src/shadow/cljs/npm/deps.clj#L70

but pretty much all this code does is maven interop via pomegranate. which is exactly what lein or boot use

can I enable any further debug / diagnostics?

unfortunately no. never had issues with this before.

could try shadow-cljs pom and then use mvn directly to resolve the deps. maybe that prints more useful info

thanks - i’ll let you know what fixes it

https://docs.aws.amazon.com/codebuild/latest/userguide/troubleshooting.html

> When you use Maven with an AWS CodeBuild provided Java build environment, Maven pulls build and plugin dependencies from the secure central Maven repository at https://repo1.maven.org/maven2. This happens even if your build project's pom.xml file explicitly declares other locations to use instead.

don't actually know if the settings.xml is used at all but that might be the reason it can't find shadow-cljs since thats on clojars not http://maven.org

AWS is quite annoying sometimes 🙂

ahem, Maven is not installed

doh. maybe try a temporary project.clj and lein?

installing maven now … might just all start to work … one min

maven isn't required by shadow-cljs so that shouldn't affect anything really

made no difference so you are right!

will try with lein

but does maven tell you anything when using the pom file?

shadow-cljs pom && mvn dependency:tree or so

I will give that a try

so I think there is something off with the JDK install

very weird indeed. no idea what would cause something like that.

https://stackoverflow.com/questions/33439905/is-the-cacerts-file-missing-in-ubuntu-15-10-and-openjdk-8-jdk

seems like a bug in ubuntu

the recommended fixes there do the job

blimey - we so often find that we are sitting on top of sand