Repository navigation
fix: raise MAX_FILE_SIZE_GB to the documented 100 GB limit - #630
Open
Kayvan-Zahiri wants to merge 1 commit into
Open
Kayvan-Zahiri wants to merge 1 commit into
Kayvan-Zahiri wants to merge 1 commit into
Conversation
check_file still rejected files above 50.1 GB even though the fine-tuning docs advertise 100 GB. Co-authored-by: Cursor <cursoragent@cursor.com>
Broly Security ScanWarning Latest baseline snapshot is stale. Broly is running in PR-only fallback mode until the next scheduled baseline refreshes. This does not block the PR. Note Re-scan this PR anytime with
|
This branch has not been deployed
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.
The fine-tuning docs say we accept files up to 100 GB, but
check_filestill usedMAX_FILE_SIZE_GB = 50.1. A 60 GB file failed the size check even though it's under the documented limit.I bumped the constant to 100 so it matches the docs.
NUM_BYTES_IN_GBis still2**30, so this is 100 GiB the same way the old 50.1 value was. Added a test that a 60 GB file now passes, and one that a file over the cap still fails.Fixes #588
Made with Cursor