-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[CLU March Preview] Tests #23524
[CLU March Preview] Tests #23524
Conversation
5f13519
to
a9252a8
Compare
...ognitivelanguage/azure-ai-language-conversations/azure/ai/language/conversations/_version.py
Show resolved
Hide resolved
...-conversations/azure/ai/language/conversations/models/_conversation_analysis_client_enums.py
Show resolved
Hide resolved
...-conversations/azure/ai/language/conversations/models/_conversation_analysis_client_enums.py
Show resolved
Hide resolved
...-conversations/azure/ai/language/conversations/models/_conversation_analysis_client_enums.py
Show resolved
Hide resolved
...cognitivelanguage/azure-ai-language-conversations/tests/async/test_conversation_app_async.py
Show resolved
Hide resolved
...guage/azure-ai-language-conversations/samples/async/sample_analyze_conversation_app_async.py
Show resolved
Hide resolved
...language-conversations/samples/async/sample_analyze_orchestration_app_conv_response_async.py
Outdated
Show resolved
Hide resolved
...language-conversations/samples/async/sample_analyze_orchestration_app_luis_response_async.py
Show resolved
Hide resolved
...ge/azure-ai-language-conversations/tests/async/test_orchestration_app_luis_response_async.py
Show resolved
Hide resolved
sdk/cognitivelanguage/azure-ai-language-conversations/tests/test_orchestration_direct.py
Show resolved
Hide resolved
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: |
fb4a1f0
to
cb897a8
Compare
API changes have been detected in |
...guage/azure-ai-language-conversations/samples/async/sample_analyze_conversation_app_async.py
Outdated
Show resolved
Hide resolved
...-language-conversations/samples/async/sample_analyze_orchestration_app_qna_response_async.py
Outdated
Show resolved
Hide resolved
...cognitivelanguage/azure-ai-language-conversations/samples/sample_analyze_conversation_app.py
Show resolved
Hide resolved
API change check for API changes have been detected in |
* add swagger.md * generate client * update swagger.md * regenerate client * samples - add conversation project sample * tmp commit * update conversations samples in both conversations and orchestration projects * update samples * update sync samples * update samples - file names and secrets * update samples readme * add async samples * update async samples * update samples * add some tests * add qna test * add async tests * update tests * update tests * fix sync tests * fixed async tests * add recorded tests * update changelog * rename body to task * update samples * update conversation samples * fix rebase * re-record tests * update samples to use input models * update and re-record tests * update swagger reference * rename confidence score * update samples * updating samples for extra info * update readme
* add swagger.md * generate client * update swagger.md * regenerate client * samples - add conversation project sample * tmp commit * update conversations samples in both conversations and orchestration projects * update samples * update sync samples * update samples - file names and secrets * update samples readme * add async samples * update async samples * update samples * add some tests * add qna test * add async tests * update tests * update tests * fix sync tests * fixed async tests * add recorded tests * update changelog * rename body to task * update samples * update conversation samples * fix rebase * re-record tests * update samples to use input models * update and re-record tests * update swagger reference * rename confidence score * update samples * updating samples for extra info * update readme
Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines