https://kotlinlang.org logo
Title
k

kioba

10/29/2020, 11:42 AM
I am getting a dependency resolution error on my PR after updating with the latest
Arrow-Core
. Is this a known issue?
one example:
Could not find io.arrow-kt:arrow-core:1.0.0-SNAPSHOT.
Searched in the following locations:
       - <https://kotlin.bintray.com/kotlinx/io/arrow-kt/arrow-core/1.0.0-SNAPSHOT/maven-metadata.xml>
       - <https://kotlin.bintray.com/kotlinx/io/arrow-kt/arrow-core/1.0.0-SNAPSHOT/arrow-core-1.0.0-SNAPSHOT.pom>
     Required by:
         project :arrow-ui-data
r

raulraja

10/29/2020, 12:06 PM
@Rachel may know, not sure what's up with that.
r

Rachel

10/29/2020, 12:14 PM
Hi @kioba 🙌 please, could you provide the link of that PR? And which check is raising that error? Thanks!
With this piece of log,
arrow-core
cannot be found in Bintray, just OSS
k

kioba

10/29/2020, 12:17 PM
this is the workflow error log: https://github.com/arrow-kt/arrow-core/pull/251/checks?check_run_id=1325822879 and this is the PR: https://github.com/arrow-kt/arrow-core/pull/251 Thank you Rachel for helping me with this 🙏
the check is
check-previous_build-integration
`Edit`:
check-previous_doc-integration
also fails
r

Rachel

10/29/2020, 12:27 PM
Thanks to you for your contributions!! Ok, I'm going to re-run both failing checks: doc integration is failing because of an error from GitHub (socket exception) and build integration is failing because of a flaky test from arrow-fx-coroutines
👍 1
And I'm going to improve the log because I realized that it's confusing
All the errors appear together at the end now. I'm going to show the entire log for every library without splitting them 👍
The error about
arrow-core
library not found happened because it was not generated (because of the error) and the rest of the libraries depend on it (Arrow libraries are not looked in OSS for integration tests)
💚 2
k

kioba

10/29/2020, 1:36 PM
Ohh wow that was super fast 😄 thanks for the help! So it was a flaky test after all? 👀 sorry for pulling you in for that
r

Rachel

10/29/2020, 1:37 PM
Nothing to apologize!! It was an error from GitHub envs and a flaky test from arrow-fx-coroutines - Thanks to you!!! 🙌