BadResponseCodeException on 'find related PRs' in CLion

[Raphael Lackner]

I tried to find the PR I created right now and I get an error with message like: 'Failed to lookup for PRs, please check the log and raise an issue.' The log is attached.

[Daniil Penkin]

Hi @rala,

Thanks for reporting this issue.

From the log I can see that Bitbucket responded with 400 (Bad Request). Unfortunately I can't reproduce this problem with any repository that I have access to. Can you try calling the very same endpoint from your browser (being logged in) or grant me access to the repo in question so that I can do that? I'm interested in the JSON payload this error returns.

In the future Linky should probably log the body in such cases...

Cheers, Daniil

[Raphael Lackner]

the response was just an empty object

[Daniil Penkin]

Thanks for checking that @rala.

I tracked it down on Bitbucket side, I need some time to clear out some details.

Just out of curiosity, does the PR lookup UI work for that commit? Can you go to that commit view and click on Go to pull request link in the side menu, something like this:

It should show a dialog with a list of PRs or some message.

Cheers, Daniil

[Raphael Lackner]

We're crunching the numbers and should be done shortly. We're indexing the repository. (or sth like that) ... and now it works

[Daniil Penkin]

Ok, this means PR indexing was triggered, i.e. you requested PR lookup for that repo for the first time.

Does Linky work now for that repo by any chance? It might be something with the initial state.

[Raphael Lackner]

yes it does - thank you

[Daniil Penkin]

Well, thank you, I appreciate your help!

What you surfaced is that the bug seems to be not in Linky but rather in Bitbucket. Still need to fix it :) I'll leave this task open until I nail it down.

Cheers, Daniil

[Chernikov Ilya]

I have the same issue (400) with Rider

[Daniil Penkin]

Fixed in version 7.2

[Daniil Penkin]

Removing version: 7.0 (automated comment)