wrong checksum with spark-sql 2.4.4 (Scala 2.12)

[jaceklaskowski]

steps

sbt version: 1.3.7

Create an empty project with the following build.sbt:

name := "wrong-checksum"

version := "0.1"

scalaVersion := "2.12.10"

libraryDependencies += "org.apache.spark" %% "spark-sql" % "2.4.4"

problem

[error] (update) lmcoursier.internal.shaded.coursier.error.FetchError$DownloadingArtifacts: Error fetching artifacts:
[error] https://repo1.maven.org/maven2/org/apache/spark/spark-sql_2.12/2.4.4/spark-sql_2.12-2.4.4.jar: wrong checksum: /Users/jacek/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/org/apache/spark/spark-sql_2.12/2.4.4/spark-sql_2.12-2.4.4.jar (expected SHA-1 ec1d629508b27dd126a3b24ce8af91e72778e16f in /Users/jacek/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/org/apache/spark/spark-sql_2.12/2.4.4/.spark-sql_2.12-2.4.4.jar__sha1, got 999be449cb7a92968bf60be68ff1c36647be0a4c)
[error] (ssExtractDependencies) lmcoursier.internal.shaded.coursier.error.FetchError$DownloadingArtifacts: Error fetching artifacts:
[error] https://repo1.maven.org/maven2/org/apache/spark/spark-sql_2.12/2.4.4/spark-sql_2.12-2.4.4.jar: wrong checksum: /Users/jacek/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/org/apache/spark/spark-sql_2.12/2.4.4/spark-sql_2.12-2.4.4.jar (expected SHA-1 ec1d629508b27dd126a3b24ce8af91e72778e16f in /Users/jacek/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/org/apache/spark/spark-sql_2.12/2.4.4/.spark-sql_2.12-2.4.4.jar__sha1, got 999be449cb7a92968bf60be68ff1c36647be0a4c)
[error] Total time: 2 s, completed Jan 16, 2020 7:05:59 PM

expectation

Spark SQL dependency resolved without disabling coursier.

notes

Disabling coursier with the following in build.sbt fixes it:

useCoursier := false

[eed3si9n]

@jaceklaskowski Thanks for the report. Could you also report it to coursier/coursier please?

[eed3si9n]

Not sure if this was resolved, but if in fact the checksum does NOT match (because it contains error message in HTML etc), then I think the default behavior of failing is the correct behavior.

[jaceklaskowski]

I don't remember whether it was fixed or not, but haven't seen it since. I think it could be marked as resolved (as can always be reopened when necessary). Thank you.