Skip to content

kotlinx-coroutines-debug-1.10.1.jar has duplicated ZIP entries #4381

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

Closed
Him188 opened this issue Mar 9, 2025 · 3 comments
Closed

kotlinx-coroutines-debug-1.10.1.jar has duplicated ZIP entries #4381

Him188 opened this issue Mar 9, 2025 · 3 comments
Labels

Comments

@Him188
Copy link

Him188 commented Mar 9, 2025

Describe the bug

Using the following script to find duplicated entries from the kotlinx-coroutines-debug-1.10.1.jar, we get:

Duplicate entries found: ['META-INF/versions/9/module-info.class']
import zipfile
from collections import Counter

def has_duplicate_entries(zip_path):
    with zipfile.ZipFile(zip_path, 'r') as zf:
        names = zf.namelist()
        duplicates = [item for item, count in Counter(names).items() if count > 1]
        if duplicates:
            print(f"Duplicate entries found: {duplicates}")
            return True
        else:
            print("No duplicate entries found.")
            return False

zip_path = '/Users/him188/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlinx/kotlinx-coroutines-debug/1.10.1/894ec9b16eb3bb3b39037afb7eb7c86e746f5844/kotlinx-coroutines-debug-1.10.1.jar'

has_duplicate_entries(zip_path)

This breaks some downstream applications, like packaging an Compose for Desktop application:
https://youtrack.jetbrains.com/issue/CMP-7734/packageReleaseDmg-for-macOS-arm64-fails-due-to-duplicated-zip-entry

Provide a Reproducer

Download the jar from Maven Central.

@Him188 Him188 added the bug label Mar 9, 2025
@dkhalanskyjb
Copy link
Collaborator

Duplicate of #4340

@dkhalanskyjb dkhalanskyjb marked this as a duplicate of #4340 Mar 10, 2025
@ilyako87
Copy link

Duplicate of #4340

Share please in which version and when it will be solved.
The resolved issue you refer to as a duplicate says that it will be included in the next release. But it was a release 1.10.0 issue and this case is a release 1.10.1 issue.

@dkhalanskyjb
Copy link
Collaborator

The next release is either 1.10.2 or 1.11.0, and it will include the fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants