HTTP 500 error SonarCloud impossible to add new repo

SonarQube Cloud
1

I’m trying to add new repo’s from our bitbucket but I have an error 500 on listing the repos. So it’s impossible to add the repos.

thanks,
Marc

2

Hey there.

Is your organization bound?

image
image2696×1286 260 KB

If so, can you open up your browser’s DevTools and see specifically what API call is failing? It would be super useful for you to provide the details of that API call that is failing.

3

Yes it is

4

image
image971×269 7.56 KB

5

I was able to look things up in the backend. Right now it appears that Bitbucket is returning Rate limit for this resource has been exceeded when SonarQube Cloud queries the https://api.bitbucket.org/2.0/repositories/ endpoint.

This appears to affect your specific organization, and not all Bitbucket organizations on SonarQube Cloud.

Is it possible that there is something else in your organization that might be continously querying Bitbucket and exceeding the rate limit?

6

Do you know which users is causing the rate limit we saw some rate limit yesterday but nothing today.

7

That’s a great question I don’t really know the answer to. My understanding is that it’s our Bitbucket OAuth application doing the querying, but I’m starting to doubt myself.

I’m going to phone a friend on this one. In the meantime, it looks like you haven’t tried since yesterday. Can you see if the issue persists today?

9

Hi @mag,

The API rate limit is only affecting your Bitbucket workspace, not all our Bitbucket users. Because those API calls are made using the Connect App credentials (the App SonarQube Cloud that you installed into your workspace when you created the org), I admit that I don’t know how Bitbucket measures API usage, their documentation not being clear about this scenario.

It can be an workspace-level API usage, or a use-level usage, and in that last case I’d say it’s the user who initially installed the App the first time (as we do not refer to the logged-in user for making those calls).

As SQC doesn’t have an heavy usage of the API, it can be that you have something else using it. We can’t say what or who, this is not an information Bitbucket shares in the HTTP response we receive.

If you want to try, the call which fails is:

Sent by DM

As @Colin mentioned, to validate this theory I would retry a few times at different moment of the day to see if it eventually works. Once we have cleared this out, you could investigate internally at what else is consuming your API usage.

Best,
Antoine

13

Hi @mag,

Happy new year! :partying_face:
Were you or will you able to make some progress here to verify if the theory of BitBucket API overuse is true?

Cheers,
Antoine

14

Hi Antoine,

thanks, happy new year to you too!

I have contacted atlassian and they confirmed it’s oauth that rate limit so i’m trying to figured out what is consuming this. I tried serveral time but impossible to scan in sonarcloud.

thanks
MAG

1 Like