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
Unreadable forms in certain eval-in-project calls #2328
Comments
I'm not sure if it's the same issue, but both eastwood and bikeshed fail for me with the same I also get this line: |
<digression warning> |
@pmonks if that path is predictable we could check for its existence before adding the flag to the |
I have done a tiny bit of investigation, and at least so far it appears that the reduce-dep-step things with |
@jafingerhut thanks; I can just locally install a snapshot version which has what I need. I'm just confused as to why certain uses of |
OK. Just in case it may be helpful, I went ahead and released Eastwood version 0.2.6-beta2 to clojars. If you run "lein eastwood lein-project" with earlier Eastwood versions, it pretty-prints the Leiningen project map, but without the metadata shown. With 0.2.6-beta2 it also shows the metadata. Running with that command line stops immediately after showing that map, without doing linting like Eastwood normally would. You can also run:
and it will print out debug info, including the Leiningen project map with metadata, and then continue linting as normal. |
@technomancy wrote:
Yeah that'd be handy, though sadly I don't think it is that predictable. My skim reading of JDK-8146115 leads me to suspect that the JVM checks a couple of different things to try to determine what the cgroups limits are. Perhaps the best path is to raise an issue against Java, asking them to shush the JVM up a bit when |
I tracked this down to a change which was applied in #2306; before that we did not print metadata when writing out code for |
Workaround to resolve reflection warning while avoiding technomancy#2328
Sometimes
eval-in-project
calls will result in forms that contain unreadable#object...
elements.I have only been able to reproduce the problem with
lein eastwood
but others report problems with built-in tasks or withlein ring
.In the instance with eastwood, somehow the entire project map is being attached as metadata to the form being evaluated, and the metadata contains merge directives like
reduce-dep-step
which is a function.The text was updated successfully, but these errors were encountered: