Skip to content

Conversation

@asamal4
Copy link
Contributor

@asamal4 asamal4 commented Jul 29, 2025

modify eval data structure as per latest multi-turn data model

Summary by CodeRabbit

  • Chores
    • Updated the evaluation data format to support multi-turn conversations.
    • Corrected a typo in the expected response for the "list_versions" evaluation.
    • Broadened the supported Python version range in the evaluation documentation.

@openshift-ci openshift-ci bot requested review from eranco74 and omertuc July 29, 2025 11:08
@coderabbitai
Copy link

coderabbitai bot commented Jul 29, 2025

Walkthrough

The evaluation data YAML file was restructured from a flat list of evaluations to a nested format, grouping each evaluation under a "conversation_group" with a "conversation" list. Additionally, a typo in the expected response for the "list_versions" evaluation was corrected. The README documentation was updated to reflect support for multi-turn evaluation and broadened the Python version requirement.

Changes

Cohort / File(s) Change Summary
Evaluation Data Structure Update
test/evals/eval_data.yaml
Restructured evaluation entries into nested "conversation_group" objects with "conversation" lists; fixed a typo in one expected response.
Evaluation Documentation Update
test/evals/README.md
Updated documentation to indicate support for multi-turn evaluations and expanded Python version compatibility range.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

Suggested labels

approved, lgtm

Suggested reviewers

  • carbonin

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 99a8968 and 880a8a9.

📒 Files selected for processing (2)
  • test/evals/README.md (1 hunks)
  • test/evals/eval_data.yaml (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • test/evals/README.md
🚧 Files skipped from review as they are similar to previous changes (1)
  • test/evals/eval_data.yaml
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Red Hat Konflux / assisted-chat-saas-main-on-pull-request
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@asamal4
Copy link
Contributor Author

asamal4 commented Jul 29, 2025

/hold
waiting on lightspeed-core/lightspeed-evaluation#22

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
test/evals/eval_data.yaml (1)

18-21: Tighten wording in the “list_versions” expected response
Minor phrasing + hyphenation fix.

-      expected_response: "There are several versions of OpenShift available. The most recent production version is 4.19, 4.20 pre release versions are available as well as several previous versions."
+      expected_response: "There are several versions of OpenShift available. The most recent production version is 4.19. Pre-release versions of 4.20 are also available, as well as several previous versions."
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between aa066dc and 99a8968.

📒 Files selected for processing (1)
  • test/evals/eval_data.yaml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Red Hat Konflux / assisted-chat-saas-main-on-pull-request
🔇 Additional comments (1)
test/evals/eval_data.yaml (1)

1-28: Double-check that the evaluation loader expects a list of conversation-group mappings

The previous format was a flat list; now each item is a mapping with the keys conversation_group and conversation.
Before merging, verify that whatever code consumes this YAML (e.g., the evaluation runner) iterates over a list rather than expecting a single top-level mapping keyed by group name – otherwise it will silently load nothing.

If the loader still expects a mapping, wrap the whole list under a new top-level key or switch to:

basic_introduction_conv:
  conversation:
    - 
basic_cluster_request_conv:
  conversation:
    - 

@asamal4 asamal4 marked this pull request as ready for review July 30, 2025 07:05
@openshift-ci openshift-ci bot requested review from carbonin and jhernand July 30, 2025 07:05
@asamal4
Copy link
Contributor Author

asamal4 commented Jul 31, 2025

/unhold
lightspeed-core/lightspeed-evaluation#22 merged now.
@carbonin PTAL

@carbonin
Copy link
Collaborator

eval: data structure as per multi-turn datamodel
@asamal4 asamal4 force-pushed the eval-multiturn-datamodel branch from 99a8968 to 880a8a9 Compare July 31, 2025 23:34
@asamal4
Copy link
Contributor Author

asamal4 commented Jul 31, 2025

Does this need to change the version in https://github.com/rh-ecosystem-edge/assisted-chat/tree/main/test/evals#prerequisites?
@carbonin I changed the python version, lsc_agent_eval (no change)

@openshift-ci
Copy link

openshift-ci bot commented Aug 1, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: asamal4, carbonin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved label Aug 1, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 7c342f8 into rh-ecosystem-edge:main Aug 1, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants