You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that we've reached a stable spot with our SDK we need to be particularly attentive to failures in the canary region, given that it's a first signal for potential larger customer issues.
The text was updated successfully, but these errors were encountered:
ghost
added
the
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
label
Dec 8, 2020
Please add a test that runs indefinitely or at least for several days to catch the production issues that customers (we) actually faced. I would say 30-60 days would be long enough, or to just keep it running until the next release is cut.
Just adding in some more context - there is conversation in this issue (#12609) that is discussing what we have and what we're putting in place for long term tests.
Update PIM specs for Documentation changes (Azure#12815)
* PIM API Specs
* update readme
* Update
* Update readme
* operation id fix
* name fix
* Name changes
* fix
* Fix
* Changes based on docs generated
* Scope fix in example
* Updates for documentation
* Change operation name
Co-authored-by: Aman Swaika <[email protected]>
This original issue was handle some specific cases that were breaking in canary. We have broken those down into specific issues that we'll handle individually (for instance, #14441).
I am closing this particular issue in favor of tracking the more specific failures that have already been logged.
@jmealo - we've actually started doing more long-term and stress related testing across all of our messaging packages. We have really appreciated your feedback across this and other issues.
Now that we've reached a stable spot with our SDK we need to be particularly attentive to failures in the canary region, given that it's a first signal for potential larger customer issues.
The text was updated successfully, but these errors were encountered: