-
Notifications
You must be signed in to change notification settings - Fork 805
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: issue#4346 #4348
fix: issue#4346 #4348
Conversation
…e is too long' errors with large payloads.
@@ -25,7 +25,7 @@ classifiers = [ | |||
dependencies = [ | |||
"Jinja2>=3.0.1", | |||
"PyYAML>=5.0", | |||
"aiohttp", | |||
"aiohttp>=3.9.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Older versions of aiohttp
(e.g. 3.8.6) don't expose the ClientSession.max_field_size
kwarg.
I've attached an example to reproduce the issue on main. Usage:
Then navigate to localhost:5001 and click on "Try it out" > "Execute" under /impute. You'll get this error on main:
|
Thanks for opening this PR. I believe this is resolved on the data container level in this PR . I will close this one |
What does this PR address?
This PR fixes issue #4346.
Before submitting:
Does the Pull Request follow Conventional Commits specification naming? Here are GitHub's
guide on how to create a pull request.
Does the code follow BentoML's code style,
pre-commit run -a
script has passed (instructions)?The exception is thatThis was a result of using a newer version of pdm (2.11.1 rather than 2.10.4, which your CICD uses). Downgrading pdm solved the issue.pdm-lock-check
failed, for reason I don't understand.Did you write tests to cover your changes?
No, but I think it would be a good idea to write a test with a sufficiently large payload that would trigger this error without the fix. But I don't know where or how to do that, so would need some guidance.