Skip to content
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

fix: Ensure the results of Orchestrator scoring are not readonly (#5763) #5764

Merged
merged 1 commit into from Jul 7, 2021

Conversation

EricDahlvang
Copy link
Member

  • Ensure the results of Orchestrator scoring can be added to for unknown intent

  • Move .ToList()

  • nullable result

Fixes #5762

* Ensure the results of Orchestrator scoring can be added to for unknown intent

* Move .ToList()

* nullable result
@EricDahlvang EricDahlvang requested a review from a team as a code owner July 6, 2021 16:59
@mrivera-ms
Copy link
Contributor

/azp run BotBuilder-DotNet-CI-PR-yaml

@azure-pipelines
Copy link

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

@mrivera-ms
Copy link
Contributor

/azp run BotBuilder-DotNet-CI-PR-yaml

@azure-pipelines
Copy link

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

@mrivera-ms
Copy link
Contributor

/azp run BotBuilder-DotNet-CI-PR-yaml

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@mrivera-ms
Copy link
Contributor

/azp run BotBuilder-DotNet-CI-PR-(MacLinux)-yaml

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@mrivera-ms mrivera-ms merged commit 8e54506 into 4.14 Jul 7, 2021
@mrivera-ms mrivera-ms deleted the eric/cherryPickOrchestratorFix branch July 7, 2021 19:04
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.

None yet

2 participants