FIX Updates to address Integration Test failures (Likert notebook + dict identifier)#1688
Open
behnam-o wants to merge 4 commits intomicrosoft:mainfrom
Open
FIX Updates to address Integration Test failures (Likert notebook + dict identifier)#1688behnam-o wants to merge 4 commits intomicrosoft:mainfrom
behnam-o wants to merge 4 commits intomicrosoft:mainfrom
Conversation
behnam-o
changed the title
behnam-o
changed the title
romanlutz
approved these changes
May 5, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
some changes to address failures in integration tests:
1- In this notebook, OpenAIResponseTarget is used right now, which does not have the supports_editable_history capability, so this notebook fails with an error saying:
ValueError: Target does not satisfy 1 required capability(ies):
E - Target does not support 'supports_editable_history' and no handling policy exists for it.
this PR fixes that by using a different target in the Likert scorer demo notebook
2- some integration test updates missed in #1685