[Observability] Update required field from 'score' to 'scores'#203584
Merged
arturoliduena merged 1 commit intoelastic:mainfrom Dec 17, 2024
Merged
Conversation
arturoliduena
added
release_note:fix
Team:Obs AI Assistant
Contributor
|
Pinging @elastic/obs-ai-assistant (Team:Obs AI Assistant) |
botelastic
bot
added
the
ci:project-deploy-observability
Contributor
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
sorenlouv
approved these changes
Dec 11, 2024
Contributor
sorenlouv
left a comment
sorenlouv
left a comment
There was a problem hiding this comment.
As discussed, having an API test to cover this would be great!
Contributor
Author
|
@elasticmachine merge upstream |
Contributor
|
merge conflict between base and head |
…reSuggestions schema
arturoliduena
force-pushed
the
fix-Error-Toolcall-arguments-for-score
branch
from
82ea9e8 to
98fd8b7
Compare
Contributor
⏳ Build in-progress
History
|
Contributor
|
Starting backport for target branches: 8.x https://github.com/elastic/kibana/actions/runs/12377322854 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Dec 17, 2024
…ic#203584) Closes elastic#203739 ## Summary fix error: `“Error scoring documents: Tool call arguments for score were invalid”` [Observability] Update required field from 'score' to 'scores' in scoreSuggestions schema (cherry picked from commit 1b52848)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
JoseLuisGJ
pushed a commit
to JoseLuisGJ/kibana
that referenced
this pull request
Dec 19, 2024
…ic#203584) Closes elastic#203739 ## Summary fix error: `“Error scoring documents: Tool call arguments for score were invalid”` [Observability] Update required field from 'score' to 'scores' in scoreSuggestions schema
benakansara
pushed a commit
to benakansara/kibana
that referenced
this pull request
Jan 2, 2025
…ic#203584) Closes elastic#203739 ## Summary fix error: `“Error scoring documents: Tool call arguments for score were invalid”` [Observability] Update required field from 'score' to 'scores' in scoreSuggestions schema
viduni94
pushed a commit
to viduni94/kibana
that referenced
this pull request
Jan 23, 2025
…ic#203584) Closes elastic#203739 ## Summary fix error: `“Error scoring documents: Tool call arguments for score were invalid”` [Observability] Update required field from 'score' to 'scores' in scoreSuggestions schema
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
4 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.
Closes #203739
Summary
fix error:
“Error scoring documents: Tool call arguments for score were invalid”[Observability] Update required field from 'score' to 'scores' in scoreSuggestions schema
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelines