{CI} Fix Azure CLI Extensions Sync to MicrosoftDocs error #5183
Conversation
This file contains hidden or 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
ghost
added
ghost
requested review from
kairu-ms
approved these changes
Aug 3, 2022
kairu-ms
reviewed
Aug 3, 2022
jsntcy
approved these changes
Aug 3, 2022
Collaborator
|
Good to know you fixed it! @wangzelin007 |
jiasli
approved these changes
Aug 3, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
The pipeline (Azure CLI Extensions Sync to MicrosoftDocs）didn't work since July 5th.
Here is the error message:
Since MarkupSafe remove soft_unicode in version 2.1.0So we use MarkupSafe == 2.0.1 to fix this error.And we use jinja2 == 3.0.3 in azure-cli which already drops the soft_unicode.
https://github.com/Azure/azure-cli/blob/75f7048672cf8198bb8f073262caa9e706b68699/scripts/ci/test_ref_doc.sh#L17
So we also upgrade jinja2 to 3.0.3 in azure-cli-extensions.
Test result: