Getting 500 error when repository list exceeds 200 in group_privileges Bitbucket API 1.0

shelbycalma

When I issue this call that returns a repository list which exceeds 200 repos, I get an HTTP 500 error.

https://api.bitbucket.org/1.0/group-privileges/team/test/groupname/

This is the response I get:

b'{"type": "error", "error": {"message": "Something went wrong", "id": "ca1abe7e9dd646bbbd18b69bb96d7df3"}}'

 

It's working If the return list is less than 200 repos.

Is there a return limit for this call?  Is there an equivalent "pagelen" parameter than I can use to paginate the return list? Is there a workaround for this? I need to get the list of repositories for each usergroup. Thanks!

tomlankhorst

I get similar issues. It seems like this error pops up whenever the backend takes more than 30 seconds to respond.

API 1.0 has been announced deprecated for multiple years, but there's no 2.0 alternative yet.

For a medium-sized organization, this call quickly returns megabytes of JSON info. Unfortunately, the lack of pagination makes the response sometimes take more than 30 seconds, which results in a 500 response.

Not only does this effectively block access to the endpoint, but it also puts needless strain on both Atlassian's and the client's servers.

When can we expect that the deprecated 1.0 endpoints get their 2.0 counterparts?

 

Thanks a lot for your time.