Hi! Starting 2-3 days ago, the `refreshVersions` t...

# refreshversions

[Emil Butiri]

Hi! Starting 2-3 days ago, the refreshVersions task fails because of an HTTP 403. Can’t figure out which repo might be causing this or how to diagnose better. This is a snippet of what I get when running it with --stacktrace :

Caused by: retrofit2.HttpException: HTTP 403 Response.error()
	at de.fayard.refreshVersions.core.internal.MavenDependencyVersionsFetcherHttp.getXmlMetadataOrNull(MavenDependencyVersionsFetcherHttp.kt:44)
	at de.fayard.refreshVersions.core.internal.MavenDependencyVersionsFetcherHttp$getXmlMetadataOrNull$1.invokeSuspend(MavenDependencyVersionsFetcherHttp.kt)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:56)
	at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:274)
	at kotlinx.coroutines.BlockingCoroutine.joinBlocking(Builders.kt:84)
	at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking(Builders.kt:59)
	at kotlinx.coroutines.BuildersKt.runBlocking(Unknown Source)
	at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking$default(Builders.kt:38)
	at kotlinx.coroutines.BuildersKt.runBlocking$default(Unknown Source)
	at de.fayard.refreshVersions.core.RefreshVersionsTask.taskActionRefreshVersions(RefreshVersionsTask.kt:58)
...

Also tried running with --debug and --info but I don’t see anything helpful (or maybe I’m missing something)

[louiscad]

Hello, please move this to GitHub issues

[Emil Butiri]

I’ll do that, thank you!

[louiscad]

Also, you can search the logs of the gradle task run for "403" and you'll find the url(s) that are the culprit. Sharing them to us could be useful for us to know what action to take.

[Emil Butiri]

Ah, yes, I think I get it now: https://scans.gradle.com/s/yx7didbhy6avi/console-log#L96 and a few others that start with “kotlin.bintray”

[Emil Butiri]

Submitted as issue as well

[Emil Butiri]

TIL how to use the build scan. Thank you! 🙂

[louiscad]

You can just remove those repos

[louiscad]

Bintray has been killed

[louiscad]

BTW, best to write your analysis in the issue

[Emil Butiri]

d’oh… so it was on my side, once I removed the bintray repos it worked

[Emil Butiri]

I’ve closed the issue now. Thank you for your help!

[Emil Kantis]

Could be useful with more graceful error handling. Logging something like <REPO> was unreachable (error code, message), no updates has been provided for dependencies using this repository. Happens to me occasionally because we have a internal repo available on VPN only.

[louiscad]

I agree. Not too high on the priority list, but I'd like to do this one day.