MacPingu

Execute Exceptions in WPS 2.0.0: http://docs.opengeospatial.org/is/14-065/14-065.html#61

WPS 1.0.0: > [..] If a process fails for some reason, the implementation raises an error and places it in the exception report included in this ProcessFailed structure. It sounds...

@eran-pinhas ... `_run_process` is also called in async mode ... but it is a bit hidden: https://github.com/geopython/pywps/blob/c351a11a4149d865308217497790d1f86991d02a/pywps/processing/job.py#L20

Adding an example with returning status code 200 and status report containing an exception report: ``` hello Say Hello Just says a friendly Hello. Returns a literal string output with...

... and here is the response using PR #446: ``` Process failed, please check server error log ``` In both cases we get the info there is something wrong but...

just got a link to "function as a service": https://dev.to/developius/functions-as-a-service---deploying-functions-to-docker-swarm-via-a-cli Haven't really looked into it ... but might be useful as an example for using docker/swarm.

@jachym @tomkralidis See PR #522.

just something a stumbled upon ... the multiproccessing module of pathos: https://github.com/uqfoundation/pathos I haven't used it by myself.

Just referencing this work with a pywps/celery demo: https://github.com/fderue/pywps_celery_demo This work was based on the scheduler extension included in pywps: https://pywps.readthedocs.io/en/master/extensions.html#job-scheduler-extension There was also a question on the pywps-dev mailing...

I have added a new process in Emu to show the usage of default values: https://github.com/bird-house/emu/pull/114 Currently the default value is used when no value is provided both for `min_occurs=0`...