Connection is shutdown when running terraform plan

[uberspot]

Hi, we use this provider to manage bitbucket repos for our Org.
This worked previously but lately when we add more repos it crashes when doing terraform plan. It seems like we reach the bitbucket api throttling limit?
For each repo we set default reviewers and 3-5 webhooks. I assume there is a request per webhook when planning/applying?

terraform -v: = 0.11.7

Panic Output

https://gist.github.com/uberspot/dddefe5842cf46305fffd58f47c93f1c#file-terraform_crash-txt

Expected Behavior

Creates one more bitbucket repository with proper webhooks etc.

Actual Behavior

Connection is refused for all modules when we run plan (after adding one extra module for one extra repo).

Steps to Reproduce

We're not sure because it is not 100% reproducible by us. If we wait long enough it might work. :/

Important Factoids

We use the bitbucket cloud api with bitbucket terraform provider.

[eduardZA]

We're seeing exactly the same. The crash log is almost identical. Also worked perfectly fine in the past.

It seems to be breaking when refreshing the state, making API calls to BitBucket to verify buckets' existence. Adding a new repository to a blank project - where no refresh is required - succeeds without a hitch.

This notice on Atlassian.com mentions the following:

With that in mind, as of June 30, 2018 the Bitbucket Cloud version 1.0 API is deprecated, and in accordance with the Atlassian REST API policy, all version 1.0 APIs will be removed from Bitbucket Cloud’s API permanently on 31 December 2018.

Deprecated, not removed yet, but still: our last successful run was on the 28th of June. No luck since then, regardless of provider versions.

Currently running:
Terraform 0.11.7
AWS Provider 1.27.0 (also tested 1.25.0)
BitBucket Provider 1.0.0

Using -parallelism=n or running terraform refresh breaks in the same way.

Has anyone had any luck resolving this, or are we going to have to wait for a provider update?