-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Error starting debugger after migration from 2.3.141 to RELEASE #50
Comments
Glad to hear you find it useful! Hmm weird, I think some dependency is conflicting with it 🤔 . How are you running it? Can you run it on a empty folder, with no deps? |
Correct, it seems to be a dependency conflict, namely Guava. I've seen this too. |
I don't think that is the case @danielsz. Mount 0.1.16 is just bringing :
I don't see any version of guava on my |
Not sure why |
Hmm that is weird, they are under dev dependencies 🤔 but I also see them on the pom. |
@danielsz ok I figured out asking on clojurians slack. Those aren't packaged inside mount, they are in the pom with |
That is true. They end up in the maven |
@danielsz I don't see ClojureScript nor the google-closure-library pulling guava.
What I have seen in the past is old guava dependency (because of dtype-next for example) conflicting with ClojureScript, but for a different reason. |
Clojurescript requires the |
It looks like @thheller added an explicit dependency on the latest Guava in Shadow-cljs as a temporary fix, to counter the shady business (pun intended) at |
This commit should fix the issue eda9c04 Now flow-storm doesn't have a hard dependency on ClojureScript, and will not pull it. |
Awesome. Thank you! |
Thanks. This made it work! Out of curiosity, before this new push, I was testing out removing some dependencies to catch where the problem was coming from, and by removing Apparently, dev-local was including Guava per this post and messing things up, perhaps triggering flow-storm dependency resolution wrongly. Thanks again. |
Thanks for the tool, it became my default debugger that starts along my project :)
After migrating to the latest version I can't start the debugger anymore. My best guess is that flow-storm calls something for cljs, which doesn't make sense since my project is Clojure only.
Version 2.3.141 works as usual.
My stack is:
Clojure 1.10.3
17.0.2-tem
When starting the debugger the following is shown:
Complete stack trace:
Thanks!
The text was updated successfully, but these errors were encountered: