fix: handle None test_ds in skipped messages count#232
Conversation
There was a problem hiding this comment.
Summary of Changes
Hello @RuixiangMa, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request addresses a runtime error that occurs when the test_ds (test dataset) variable is None, specifically when split-eval is disabled by default. It introduces a modification to the prepare_data.py script to safely calculate the total number of messages, ensuring the application continues to function correctly under these conditions and avoids crashes related to None type operations.
Highlights
- Error Handling: Correctly calculates the total number of messages when
test_dsisNoneto prevent aTypeErrorin the skipped messages count print statement.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Code Review
This pull request correctly fixes a TypeError that occurs when test_ds is None by adding a conditional check. The fix is effective. I've added one suggestion to improve the clarity of the new variable name and the associated log message to avoid potential confusion.
| total_messages = len(train_ds) + (len(test_ds) if test_ds is not None else 0) | ||
| print( | ||
| f"Skipped {total_skipped_count}/{len(train_ds)+len(test_ds)} messages for {dataset_name}" | ||
| f"Skipped {total_skipped_count}/{total_messages} messages for {dataset_name}" | ||
| ) |
There was a problem hiding this comment.
While this change correctly fixes the bug, the variable name total_messages is a bit misleading as it represents the total number of conversations (or dataset items), not the total number of messages within them. The resulting log message Skipped {X}/{Y} messages is ambiguous because it compares a count of skipped messages (X) to a count of conversations (Y).
To improve clarity and maintainability, I suggest renaming the variable to be more specific and updating the log message to reflect what is being counted.
| total_messages = len(train_ds) + (len(test_ds) if test_ds is not None else 0) | |
| print( | |
| f"Skipped {total_skipped_count}/{len(train_ds)+len(test_ds)} messages for {dataset_name}" | |
| f"Skipped {total_skipped_count}/{total_messages} messages for {dataset_name}" | |
| ) | |
| total_conversations = len(train_ds) + (len(test_ds) if test_ds is not None else 0) | |
| print( | |
| f"Skipped {total_skipped_count} messages across {total_conversations} conversations for {dataset_name}" | |
| ) |
Motivation
The problem occurs when test_ds is None due to split-eval being False by default

Modifications
Explicitly handles the case when test_ds is None
Related Issues
Accuracy Test
Benchmark & Profiling
Checklist