-
Notifications
You must be signed in to change notification settings - Fork 117
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
BoundingBox input types cannot be serialised to submit to Slurm cluster #610
Comments
I have the same problem now: First I had a general issue with getting the BBOX parameter work, but this was to my own mistake. But now I have the same problem with the CRS not being serializable. It happens very randomly: I can submit a job with the following input:
It gets accepted and runs. After a few more executions I suddenly get this answer:
and the log file tells me:
To make it execute again or at least not get an error is to remove the CRS from the BBox input like this:
I am calling the service asynchronously and have pyWPS integrated into a flask app that is run via gunicorn and exposed via nginx. The same as described in the Howtos for production system. I suspect it has to do if jobs are immediately executed by a worker or put into a local queue. It is all very sporadic and my feeling is that increasing the number of workers helped, but the whole pyWPS interface degrades over a time |
Could it be a problem with the BBox input serialisation if it needs to be scheduled via a queue? |
My further investigations It fails at: |
* Fixed the JSON encoding of the CRS type which crashed when the execution request was serialized * Fixed the JSON encoding of the CRS type by making sure the CRS is always set as string when parsing input Also added tests * Changed converting the string conversion of the crs input to calling the getcodeurn() method directly * Now setting bbox CRS handles None values properly
fixed by PR #650 |
Description
When sending a Bounding Box input type to the WPS server, it fails with an error:
This seems to happen when trying to submit jobs to a Slurm cluster - so serialisation is required before submitting to Slurm, and it cannot do that.
Environment
Steps to Reproduce
I am connecting from a GUI that posts the request, not sure how to reproduce.
Additional Information
I was able to fix if I make these two hacks to
owslib
andpywps
:I don't really know what these hacked lines do but it gets things working.
I'm happy to provide more info and test when I have more time.
The text was updated successfully, but these errors were encountered: