This repository has been archived by the owner on Nov 1, 2023. It is now read-only.
Potential solution for TLS errors in OneFuzz #2087
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
stishkin
requested review from
Porges,
chkeita,
mgreisen,
tevoinea,
nharper285 and
AdamL-Microsoft
mgreisen
approved these changes
Jun 27, 2022
Porges
approved these changes
Jun 27, 2022
|
@stishkin perhaps put a link to the GitHub issue in a comment, I'll add a suggestion |
Porges
reviewed
Jun 27, 2022
Co-authored-by: George Pollard <porges@porg.es>
tevoinea
approved these changes
Jun 28, 2022
ghost
locked as resolved and limited conversation to collaborators
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.
used proposed solution from here:
Azure/azure-functions-durable-python#194 (comment)
Initially ran for couple of days "pre-fix" deployment and got TLS errors in app insights.
Ran 3 day deployment of multiple jobs with the fix - got no TLS errors. Also ran check-pr and app insights had no TLS errors there.