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
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
Due to the inconsistent versions of jinja2 required by aosm and alias, and the random order of extension installations, installing a lower version of jinja2 can result in the following error:
File "/mnt/vss/_work/1/s/env/lib/python3.11/site-packages/jinja2/filters.py", line 13, in <module>
from markupsafe import soft_unicode
ImportError: cannot import name 'soft_unicode' from 'markupsafe' (/mnt/vss/_work/1/s/env/lib/python3.11/site-packages/markupsafe/__init__.py)
Therefore, i want to enforce the use of a higher version of jinja2 for codegen coverage.
Description
Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature
This checklist is used to make sure that common guidelines for a pull request are followed.
This task has bad design. It should not install all extensions in the same env and expects every extension works fine. We'll likely encounter another dependency conflict in the future.
This task has bad design. It should not install all extensions in the same env and expects every extension works fine. We'll likely encounter another dependency conflict in the future.
We need to install all extensions to calculate code generation coverage.
If the problem occurs again, consider not installing the extension that uses the lower version of the dependency.
Looks good as a workaround.
This task has bad design. It should not install all extensions in the same env and expects every extension works fine. We'll likely encounter another dependency conflict in the future.
We need to install all extensions to calculate code generation coverage. If the problem occurs again, consider not installing the extension that uses the lower version of the dependency.
I feel the reliable way is to install, calculate and then uninstall each extension modules one by one and finally sum up the whole result from extension modules.
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.
microsoft-github-policy-service
bot
requested review from
yonzhan,
jiasli,
kairu-ms,
jsntcy,
bebound and
Pan-Qi
Related command
Due to the inconsistent versions of jinja2 required by aosm and alias, and the random order of extension installations, installing a lower version of jinja2 can result in the following error:
Therefore, i want to enforce the use of a higher version of jinja2 for codegen coverage.
Description
Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.