-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pin Crypto Temporarily #21950
Pin Crypto Temporarily #21950
Conversation
…UsePythonVersion task
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment: |
It's a transient failure, overriding and merging. |
/check-enforcer override |
…into add_body_error * 'main' of https://github.com/Azure/azure-sdk-for-python: (74 commits) Pin Crypto Temporarily (Azure#21950) [release-helper] check `default tag` and `target tag` consistency (Azure#21952) [EventHubs] remove unused import (Azure#21949) [KV] Use shared test-resources.json (Azure#21940) [EventHubs] Fix pylint and mypy (Azure#21939) fix line in general document sample code (Azure#21936) Pipeline auto-discover stress test (Azure#21917) resolve the issue the bad condition in dump proxy logs (Azure#21947) [KV] Correctly fetch private RSA key material (Azure#21938) doc (Azure#21830) Sync eng/common directory with azure-sdk-tools for PR 2348 (Azure#21919) [EventHubs] ensure ownership arg does not mutate (Azure#20008) Fix the type for LROPoller wait timeout (Azure#21913) [EventHubs]Update async samples (Azure#21857) [AutoRelease] t2-containerservice-2021-11-25-33508 (Azure#21891) update for Go (Azure#21898) [pipeline] SDK Release helper : 0.0.1 (Azure#21888) [AutoRelease] t2-subscription-2021-11-25-24271 (Azure#21892) Release issue status (Azure#21887) [AutoRelease] t2-datafactory-2021-11-20-87712 (Azure#21840) ...
* resolve for 90+% of the packages. the true solution is to stop using UsePythonVersion task
The true path forward will be one of two options.
UsePythonVersion
in favor of our own hand-rolled version. It's not too bad, couple hours.For those of you that are lost. The timeline of events:
The reason behind this is that the
UsePythonVersion
task is hardcoded to go afterpypy w/2.7
orpypy w/3.6
ONLY. It legit doesn't even parse the versionspec.