Server setting to allow for bigger payloads for Processess about pygeoapi

[tomkralidis]

@supermaro84 thanks for the report. Can you provide a test case/test data which we can reproduce locally?

[supermaro84]

Hi @tomkralidis.
Thanks for quick reply.
I have created a process plugin with inputs defined as 'inputs': {
'features': {
'title': 'features',
'description': 'Description.',
'minOccurs': 1,
'maxOccurs': 1,
'schema': {
'type': 'object'
}}
},

Then a json such as :
{"inputs":{"features":[{"attributes":{"latitude":63.4,"longitude":8.7,"objectId":1}},{"attributes":{"latitude":63.4,"longitude":8.7,"objectId":1}}]
}}
the list with features works with length of 86 but it crashes with 87. I could shorten the latitude element and it works. So definitely there must be a length limit.
For testing purposes the objects in the features lists are identical.

[tomkralidis]

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.

[supermaro84]

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.