-
Notifications
You must be signed in to change notification settings - Fork 307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update/DF-20817 bitgo anchorage cbp rate limits #3592
Update/DF-20817 bitgo anchorage cbp rate limits #3592
Conversation
…se-prime well under their max API limits
🦋 Changeset detectedLatest commit: c5a5184 The changes in this PR will be included in the next version bump. This PR includes changesets to release 6 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
|
|
|
Can merge this without soak tests since there seems to be an issue with the infra |
|
|
As a separate point, did we decided we wanted to increase the number of retries as discussed too? |
I'm wondering why |
|
|
@karen-stepanyan good point let me do some more digging |
@cawthorne just checked the original messaging and it doesn't seem like we asked to override # retries in multi-address-list. Would probably need to move the cron time as well but it's a bit delicate |
|
@karen-stepanyan looks like 8 req/background execute for bitgo |
|
|
|
merging despite soak tests as there appears to be an issue with infra |
Closes #DF-20817
Description
updated default rate limits for bitgo, anchorage, and coinbase-prime
Steps to Test
Quality Assurance
infra-k8s
configuration file.adapter-secrets
configuration file or update the soak testing blacklist.test-payload.json
file with relevant requests.feature/x
,chore/x
,release/x
,hotfix/x
,fix/x
) or is created from Jira.