-
-
Notifications
You must be signed in to change notification settings - Fork 259
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
Server setting to allow for bigger payloads for Processess #1619
Comments
@supermaro84 thanks for the report. Can you provide a test case/test data which we can reproduce locally? |
Hi @tomkralidis. Then a json such as : |
Can you provide a full test case to test further (this includes a minimal Python process and a sample payload). Similar use cases work fine with much larger payloads. |
Hello. Sorry for late response but I have resolved this issue. It turned out that a method implemented in custom prosessor class was called and failed (due to failing request to external service). Sorry for this confusion. But i guess that this error would probably need to be intercepted. Thanks for help anyway. |
Description
I am experiencing that there is a limitation on json payload that is sent to processess endpoint. I am sending in an object with longer list of coordinates and I get ERROR - Expecting value: line 1 column 1 (char 0) which refers to pygeoapi/process/manager/base.py:307, which suggests that json is not well formed. Is there a setting that allows for adjusting this length? The same behaviour is experienced when using both development server and docker image.
Steps to Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
dd
Screenshots/Tracebacks
If applicable, add screenshots to help explain your problem.
Environment
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: