-
Notifications
You must be signed in to change notification settings - Fork 391
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
java.util.zip.ZipException: error in opening zip file (on npm dependency with Kotlin/JS) #537
Comments
Something very similar seems to happen if the dependency tree of a Kotlin/JVM project contains artifacts of type
when running |
Any progress on this? This fails on all my Kotlin/JS projects or multiplatform projects as soon as there is an npm dependency involved. Is there any way to work around it? |
Because of this bug regarding NPM dependencies: Kotlin/dokka#537
Because of this bug regarding NPM dependencies: Kotlin/dokka#537
NVM, seems caching sometimes prevents the spam of warnings rather than this being a fix. |
This is still occurring with Dokka 1.4.0 in multiplatform projects apparently: I haven't reproduced in the minimal Kotlin/JS project I mentioned in the initial description of this issue, though. |
Here's another minimal sample project that reproduces this issue: It seems like these exceptions occur if the compile classpath contains anything that isn't a jar / zip file. I traced it to this line in EnvironmentAndFacade.kt which adds everything from the classpath to the analysis environment, regardless of whether it's actually something that can be analyzed. |
I am also experiencing this issue w/ a MultiModule JVM-only build
What's interesting is this only seems to be an issue the first run after a clean, so if I run
I see this issue, but if I then subsequently run
it usually seems not to be there. I'm also seeing a fair deal of memory-related issues, like this output when running with the
Gotten stuck in some loops / locked up daemons that end up being reported as This is on a box with 64gb of RAM, where I do not otherwise see many / any issues running out of memory. |
Anything any of us out in the user community can do to help resolve this issue? I'd really love to highlight dokka docs for https://github.com/micronaut-projects/micronaut-kotlin/tree/master/kotlin-extension-functions but this is a major thorn in doing so. I will read up on Contributing and see if I can step debug enough to figure out what I'm looking at but I'm afraid debugging gradle tasks is not my area of expertise. |
This warning is definitely still happening on 1.4.30, perhaps it's just related to interplay w/ GraalVM? It isn't blocking completion of the |
For this build script: Line 47 imports Winston:
Without that import, both But when I add it:
And if I inject the
|
Wow, so cool that this is finally fixed. Looking forward to the release! 😄 |
Will this fix be part of release 1.6.20? Do you have any ETA for this? |
See https://github.com/Kotlin/dokka/releases/tag/v1.6.10, it's already part of version 1.6.10. |
Yeah, I'm already building a large multiplatform project with it. |
Oh I would have sworn I had tested it on 1.6.10. I guess it was on 1.6.0, my bad. In any case, thanks! This is great news! |
Describe the bug
I have a basic Koltin/JS project with the
sockjs-client
NPM dependency, and there is a Kotlin file in themain
source set defining the Kotlin external declarations for it.When running
./gradlew clean dokka
via Gradle wrapper 6.0, the build fails with an exception:Expected behaviour
The build doesn't throw an exception and the doc is properly generated, ignoring
sockjs-client
as it doesn't have any documentation.To Reproduce
I created a simple project that reproduces the issue, but had a hard time getting it to consistently reproduce the issue. The gradle cache sometimes messes with reproduction, I'm not entirely sure why.
You can see the problem in this Travis CI build.
./gradlew dokka
clean
and delete the.gradle/
folders, because the bug may not show up otherwiseDokka configuration
This simple basic config allows to reproduce the issue (again, please see example project).
Installation
Additional context
I had the original issue in the Krossbow project (a personal real-life project). This build reproduces the issue.
The issue was also mentioned in the following Slack thread:
https://kotlinlang.slack.com/archives/C0F4UNJET/p1575545943024600
The text was updated successfully, but these errors were encountered: