🐛(y-provider) use CONVERSION_FILE_MAX_SIZE settings#1913
Merged
Conversation
The settings CONVERSION_FILE_MAX_SIZE was not used in the y-provider, which caused a 413 Payload Too Large error when trying to convert a file larger than 500kb. This commit updates the y-provider to use the CONVERSION_FILE_MAX_SIZE settings, allowing it to handle larger files without throwing an error. CONVERSION_FILE_MAX_SIZE should follow the same value as the one defined in the backend settings, which is 20mb by default.
53d613a to
e323af2
Compare
lunika
approved these changes
Feb 24, 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
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.
Purpose
The settings
CONVERSION_FILE_MAX_SIZEwas not used in the route conversion in they-providerserver, which caused a413 Payload Too Largeerror when trying to convert a file larger than 500kb.This commit updates the y-provider to use the
CONVERSION_FILE_MAX_SIZEsettings, allowing it to handle larger files without throwing an error.CONVERSION_FILE_MAX_SIZEshould follow the same value as the one defined in the backend settings, which is 20mb by default.