Skip to content
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

Spark 1.2.0 dependency checksum fail #1802

Closed
kul opened this issue Jan 18, 2015 · 3 comments
Closed

Spark 1.2.0 dependency checksum fail #1802

kul opened this issue Jan 18, 2015 · 3 comments

Comments

@kul
Copy link
Contributor

kul commented Jan 18, 2015

I suppose this is happening only with lein. For dependency [org.apache.spark/spark-core_2.10 "1.2.0"], downloading jars fail with

Caused by: org.sonatype.aether.transfer.ArtifactTransferException: Could not transfer artifact org.apache.spark:spark-core_2.10:pom:1.2.0 from/to central (https://repo1.maven.org/maven2/): Checksum validation failed, expected ./spark-core_2.10/1.2.0/spark-core_2.10-1.2.0.pom: but is bd943cf1637b461bbc63154264229b1f023b7d24
        at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:951)
        at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:941)
        at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:669)
        at org.sonatype.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:60)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        ... 1 more
@kul
Copy link
Contributor Author

kul commented Jan 18, 2015

This is reproducible since 2.4.2 till master.

@hypirion
Copy link
Collaborator

This is because their pom md5 is not an md5 checksum (well, it isn't just an md5 checksum, which is the problem). You should file a bug report to Apache Spark that their pom MD5 for said version is broken, so that they avoid the problem in the future.

To turn off failing during checksum checks, add this to the project map:

:checksum :warn

It should be obvious that this is not recommended, so if they manage to fix the issue, either during this release or in the future, you should remove said line.

@kul
Copy link
Contributor Author

kul commented Jan 18, 2015

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

No branches or pull requests

2 participants