API Calls that take more than 30 seconds fail with HTTP

Issue Summary

API Calls that take more than 30 seconds fail with HTTP 500 instead of timeout message

Steps to Reproduce

1. Make an API call that would take more than 30 seconds (ex: huge commits messages)

Expected Results

1. a timeout error is shown

Actual Results

1. HTTP 500 error

Workaround

No workaround as this is a limitation of Bitbucket API

EDIT Can this API timeout limit be increased past 30 seconds? For users with large workspaces who need to make calls to list repositories/users, the amount of JSON data returned in the HTTP response can actually cause this timeout to occur and does not support scalability very well.