Skip to content

conversation sdk#20690

Closed
mshaban-msft wants to merge 28 commits intoAzure:mainfrom
mshaban-msft:feature/cognitiveservices/language/conversation
Closed

conversation sdk#20690
mshaban-msft wants to merge 28 commits intoAzure:mainfrom
mshaban-msft:feature/cognitiveservices/language/conversation

Conversation

@mshaban-msft
Copy link
Contributor

@mshaban-msft mshaban-msft commented Sep 14, 2021

continuing the work of @annatisch
original PR link here

notes:
latest swagger

  • repo: here
  • branch: feature/cognitiveservices/language
  • path: /specification/cognitiveservices/data-plane/Language/
  • file: preview/2021-07-15-preview/analyzeconversations.json

@check-enforcer
Copy link

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:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

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:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run python - [service] - ci

@mshaban-msft mshaban-msft changed the base branch from conversations_initial_sdk to feature/conversations_initial September 15, 2021 16:57
@mshaban-msft mshaban-msft force-pushed the feature/cognitiveservices/language/conversation branch 2 times, most recently from 0379bcc to 44f1d68 Compare September 28, 2021 21:27
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you give more instructions on how to create a CLU resource

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When you add the samples, can you add them with the name that doesn't have "test" in it? For example, can this sample be named Ask A Question instead of Test Deepstack?

iscai-msft and others added 21 commits September 29, 2021 15:44
…into feature/conversations/initial

* 'main' of https://github.com/Azure/azure-sdk-for-python: (273 commits)
  [purview scanning] new release by new LLC version (Azure#20823)
  [Purview catalog] release for new api-version `2021-09-01` (Azure#20822)
  disable regression testing for beta version of questionanswering (Azure#20924)
  Oct release (Azure#20890)
  Sync eng/common directory with azure-sdk-tools for PR 2046 (Azure#20911)
  [ServiceBus] Add large message support to SBAdministrationClient (Azure#20812)
  fix CI (Azure#20936)
  Update Monitor Query README and logs query client comments (Azure#20933)
  [formrecognizer] Fix v2 custom forms tests (Azure#20923)
  Resolving Build Warnings (Azure#20887)
  [eng] have verify autorest warn instead of raise (Azure#20913)
  [rest] add response backcompat mixin (Azure#20827)
  [formrecognizer] Add prebuilt-document samples and tests (Azure#20894)
  [formrecognizer] regenerate on latest (Azure#20867)
  Small tweaks to Monitor Query SDK README (Azure#20905)
  [AutoRelease] t2-netapp-2021-09-22-09782 (Azure#20783)
  [AutoRelease] t2-extendedlocation-2021-09-22-24922 (Azure#20782)
  Python 2.7 warning (Azure#20895)
  [Perf] keyvault-secrets test improvements (Azure#20900)
  Add Python 2 deprecation on front page (Azure#20799)
  ...
@mshaban-msft mshaban-msft force-pushed the feature/cognitiveservices/language/conversation branch from c7ffa9e to b2ae871 Compare September 29, 2021 19:51
@mshaban-msft mshaban-msft changed the base branch from feature/conversations_initial to feature/conversations/initial September 29, 2021 19:51
@mshaban-msft mshaban-msft changed the base branch from feature/conversations/initial to main September 29, 2021 19:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants