Fix LiveCodeBench crashes with type safety and list conversion#137
Merged
neginraoof merged 1 commit intomlfoundations:mainfrom Dec 23, 2025
Merged
Conversation
LiveCodeBench, LiveCodeBenchv5, LiveCodeBenchv5_official
Contributor
Author
|
Hi @neginraoof, could you please take a quick look at my PR when you have time? Thanks! |
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
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.
Summary
Fixes #136 by adding robust type checking and ensuring dataset is properly converted to list format.
Problem Solved
LiveCodeBench variants could crash or behave unexpectedly due to:
Changes
Files Modified:
eval/chat_benchmarks/LiveCodeBench/eval_instruct.pyeval/chat_benchmarks/LiveCodeBenchv5/eval_instruct.pyeval/chat_benchmarks/LiveCodeBenchv5_official/eval_instruct.pyKey Improvements:
examples = list(examples_dataset)isinstance(example, dict)checksCode Changes
Impact
✅ Prevents runtime crashes from type mismatches
✅ More robust error handling and logging
✅ Better debugging experience
✅ No functional changes to working cases