Open
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR enforces UTF-8 encoding when reading files in the Berkeley Function Call Leaderboard (BFCL) evaluation step to prevent encoding-related errors during test execution.
Changes:
- Updated the gorilla.patch file to explicitly specify UTF-8 encoding when opening files in the BFCL evaluation utilities
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
pgladkows
approved these changes
Feb 2, 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.
🛠 Summary
CVS-180052
Enforcing utf-8 encoding on bfcl eval step by changing patch we apply before tests
🧪 Checklist
``