When there is a corrupted jar in Maven's local repo, it will fail

[panbingkun]

When there is a corrupted jar in Maven's local repo, it will fail

[eed3si9n]

@panbingkun Thanks for the report. Please see https://www.scala-sbt.org/1.x/docs/GitHub-Actions-with-sbt.html#Caching for the recommendation on setting up the cache for GitHub Actions. In general I would recommend against the use of Resolver.mavenLocal if it contains any partial external artifacts.

Also the dependency resolution is delegated to Coursier, so could you report this issue to coursier/coursier as well plz, if you would like to have any action taken?

[panbingkun]

@eed3si9n Thank you for your reply so quickly!
In fact, before I reported the bug to here, I made many attempts

1. We override the default CachePolicy from Vector(CachePolicy.LocalUpdateChanging, CachePolicy.LocalOnly, CachePolicy.Update) to Vector(CachePolicy.Update), as follows:
   https://github.com/apache/spark/pull/42961/files#diff-6f545c33f2fcc975200bf208c900a600a593ce6b170180f81e2f93b3efb6cb3eR310

2. In our Spark build, local Maven repo was skipped in some workflows, as follows:
   https://github.com/apache/spark/pull/44516/files#diff-6f545c33f2fcc975200bf208c900a600a593ce6b170180f81e2f93b3efb6cb3eR272

All of the above can make GA pass, but none of them are perfect.

Especially when we observe some dependencies, it seems that they are not introduced by us in Spark, but rather dependencies of some tools themselves, eg:

This problem has been bothering us for a long time, since version 1.9.4 of SBT.

Besides the methods we tried above, is there a better way to help us get around it?
Thank you very much!