-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"No ns form found ..." when using boot-reload #103
Comments
Need more info. I have not seen this. |
@pandeiro Are you still seeing this? I'm going to close this if there's no more info. |
I'm seeing it too. Exception is:
Dependencies
task we're running
|
I'm yet to see this myself. A start would be to have a test project where you can reproduce this so that I could try to reproduce this. |
@wagjo Are you able to reproduce this reliably? How frequently do you see this? It would be great if we could create a sample repo for Juho to look at. |
Nope, I only get this error in about 5% of runs. |
I think I might be getting the same bug - on Travis CI sometimes the build fails after successful run, even if nothing changed. E.g. https://travis-ci.org/mjmeintjes/boot-react-native/builds/109811514 vs https://travis-ci.org/mjmeintjes/boot-react-native/builds/109810642 (same source code, just merged branch). |
I think there is a chance that recent change in Boot-reload 0.5.0 might have fixed this: adzerk-oss/boot-reload@9f430b2 |
I have not seen this myself in 5 months and I don't recall anyone at work mentioning this since the change, so I'll presume this was fixed. |
Except Boot-cljs-repl still uses the old way to inject code to the build: https://github.com/adzerk-oss/boot-cljs-repl/blob/master/src/adzerk/boot_cljs_repl.clj#L168 |
A very rare (maybe 5% or less of the time) bug I am hitting when using boot-cljs, boot-reload and multiple
cljs.edn
builds is the "No ns form found ...". It appears that the file that boot-reload is injecting prior to cljs compilation is empty when the(cljs ...)
task tries to compile it:Could this be related to some race condition with the
cljs
task? The low reproducibility suggests something like that to me, prior to going into theimpl.cljs
and inspecting.The text was updated successfully, but these errors were encountered: