Error when probing Bitbucket Server Mirror instance
Issue #83
resolved
Getting the following error whenever I start IntelliJ. Using version 2019.2.4
[unexpected case] No Bitbucket Server found at 'https://bitbucket-mirror-au.internal.atlassian.com/stash/'
com.atlassian.bitbucket.linky.rest.BitbucketRestException: Unrecognised Bitbucket client error
at com.atlassian.bitbucket.linky.rest.ExceptionsKt.mapException(exceptions.kt:58)
at com.atlassian.bitbucket.linky.rest.ExceptionsKt.mapException$default(exceptions.kt:44)
at com.atlassian.bitbucket.linky.rest.server.ConnectivityTestApiImpl$unauthenticatedResource$1.invoke(ConnectivityTestApiImpl.kt:34)
at com.atlassian.bitbucket.linky.rest.server.ConnectivityTestApiImpl$unauthenticatedResource$1.invoke(ConnectivityTestApiImpl.kt:10)
at com.github.kittinunf.fuel.core.DeserializableKt$response$2.invoke(Deserializable.kt:106)
at com.github.kittinunf.fuel.core.DeserializableKt$response$2.invoke(Deserializable.kt)
at com.github.kittinunf.fuel.core.DeserializableKt$response$asyncRequest$1$1.invoke(Deserializable.kt:193)
at com.github.kittinunf.fuel.core.DeserializableKt$response$asyncRequest$1$1.invoke(Deserializable.kt)
at com.github.kittinunf.fuel.core.RequestExecutionOptionsKt$sam$java_lang_Runnable$0.run(RequestExecutionOptions.kt)
at com.github.kittinunf.fuel.core.DefaultEnvironment$callbackExecutor$1.execute(Environment.kt:16)
at com.github.kittinunf.fuel.core.RequestExecutionOptions.callback(RequestExecutionOptions.kt:43)
at com.github.kittinunf.fuel.core.DeserializableKt$response$asyncRequest$1.invoke(Deserializable.kt:190)
at com.github.kittinunf.fuel.core.DeserializableKt$response$asyncRequest$1.invoke(Deserializable.kt)
at com.github.kittinunf.fuel.core.requests.RequestTaskCallbacks.call(RequestTaskCallbacks.kt:29)
at com.github.kittinunf.fuel.core.requests.RequestTaskCallbacks.call(RequestTaskCallbacks.kt:20)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $
at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:226)
at com.google.gson.Gson.fromJson(Gson.java:927)
at com.google.gson.Gson.fromJson(Gson.java:892)
at com.atlassian.bitbucket.linky.rest.server.ConnectivityTestApiImpl$unauthenticatedResource$$inlined$responseObject$1.deserialize(FuelGson.kt:79)
at com.github.kittinunf.fuel.core.ResponseDeserializable$DefaultImpls.deserialize(Deserializable.kt:39)
at com.atlassian.bitbucket.linky.rest.server.ConnectivityTestApiImpl$unauthenticatedResource$$inlined$responseObject$1.deserialize(FuelGson.kt:78)
at com.github.kittinunf.fuel.core.DeserializableKt$response$asyncRequest$1$deliverable$1.invoke(Deserializable.kt:189)
at com.github.kittinunf.result.Result$Companion.of(Result.kt:116)
at com.github.kittinunf.fuel.core.DeserializableKt$response$asyncRequest$1.invoke(Deserializable.kt:189)
... 7 more
Caused by: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $
at com.google.gson.stream.JsonReader.beginObject(JsonReader.java:385)
at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:215)
... 15 more
Comments (6)
-
staff -
staff - changed title to Error when probing Bitbucket Server Mirror instance
-
staff Issue
#84was marked as a duplicate of this issue. -
staff Issue
#86was marked as a duplicate of this issue. -
staff - removed version
Removing version: 8.0.101 (automated comment)
-
staff - changed status to resolved
Fixed in versions 8.0.112 (compatible with 2019.2), 8.1.113 (compatible with 2019.3) and 8.1.113.eap (compatible with 2020.1 EAP).
- Log in to comment
Hey @Hugo G ,
Thanks for reporting!
Yeah this is on my radar already, will fix it in the next release. The workaround for now is to add the actual upstream as a separate remote for that repo, like this:
Linky will discover stash.a.c and use this URL for links. You’ll still see the error you mentioned in the logs though.
Cheers,
Daniil