-
Notifications
You must be signed in to change notification settings - Fork 4
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
Error "Request Entity Too Large" #559
Comments
This build id is no longer available. |
I did ask the question in surrealdb discord channel, but no luck yet. |
I think it can be solved by increasing the size of |
I will reproduce the issue and test it |
Surely it's not a Micronaut *server* setting. It may be the client one |
I tried the same conda file to reproduce this error but there was no error in dev, it maybe because of the surreal updated version |
finally able to reproduce the error, will work on fix now |
opened issue with surreal team |
Have you tried the setting https://micronaut-projects.github.io/micronaut-docs-mn2/2.0.3/guide/configurationreference.html |
Not yet, thank you i will try now |
still same error |
I have tried the following options, but no luck:
|
We have hit issue one year back also |
we are using java 17 in micronaut 4 |
Which is the current max allowed length? is the limitation coming from the protocol? http vs websocket? |
current limit is 16kb |
Then let's add a truncation of content longer > 16k here for now wave/src/main/groovy/io/seqera/wave/controller/ContainerController.groovy Lines 307 to 309 in 5170386
|
We only need to truncate them when saving, so it is better to truncate here wave/src/main/groovy/io/seqera/wave/service/persistence/impl/SurrealPersistenceService.groovy Line 150 in 760f217
|
You are right |
It would be better to solve this using Surreal SQL statement, instead of truncating the Conda env. |
ok sure, i will work on it |
Tried different ways to add it using SQL, the issue is paring of containerfile
I changed it to the bytes which works, but then it will break the decoding when loading the objects from surrealdb I will dig further to find better solutions |
Submitting a build request using a large Conda environment, the following error is thrown:
The build raising this error is the following https://wave.seqera.io/view/builds/90d5550d6507c09c_1
The text was updated successfully, but these errors were encountered: