This repository has been archived by the owner on Jun 20, 2024. It is now read-only.
test backpressure in staging #176
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
clobber the existing staging branch 👍 |
|
I force-pushed to staging. and will deploy there once the docker image builds so that there's a bit of data to observe when you get online |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Is the testing version of #160
Not sure the procedure here for evaluation during testing. A few questions:
feat/backpressure, clobbering the existing branch, etc.)?feat/backpressurehow should I propagate those to staging? New PRs doing a revert-old + apply-new or force pushing?cc @willscott @guanzo