search

bird-house / pyramid-phoenix

Phoenix is a Pyramid web-application to make it easy to interact with WPS services
http://pyramid-phoenix.readthedocs.io/en/latest/
Apache License 2.0
7 stars 10 forks source link

Store the inputs used for failed processes #131

Open tomLandry opened 7 years ago

tomLandry commented 7 years ago

At the moment, only the log is available for failed processes. That log doesn't contain any information on inputs used. The inputs could be persisted to ease debugging or reproduction of the problem. The same logic could be applied for the "restart" option, even knowing it will probably fail again if no modification were applied to the implementations.

cehbrecht commented 7 years ago

The inputs/outputs are taken from the lineage info in the wps response xml document. I thought the lineage info was only available in case of a successful process ... that is why these infos are missing.

But i have seen cases now when the wps answers with a failure message including the input lineage. So, i can add this to phoenix.

You can see the status document by clicking on "status location" for async jobs.

On the development branch of phoenix there is now a "View as XML" tab in the details view which shows the xml response document (both for sync and async): https://mouflon.dkrz.de/monitor/details/df4090ed078549b183e4fdfc1f469070/xml

In cases where i don't get the lineage info i could store the "execute request" in the phoenix session.

As a developer you can see error messages in the pywps logs.

tomLandry commented 7 years ago

I would have labeled this issue as "improvement", don't think I have permission to do so. This is not really important, juste a note.

I've seen the "View as XML" on Mouflon. I'll fetch that soon.