#222 Callback functionality marks successful jobs as error jobs

[strauberry]

Hi,
according to my Skype chat with Zoltan, I document a bug we identified within the DRIHM project: a submitted job is executed successfully, but the portal flags this job as "error" because of "Could not exteact outputsand: localoutputz.tgz". The "fix" is the following:

Go to DCI Bridge's admin interface.
Select DCI Bridge.
Select Settings.
There is a "Callback url for status sending" property.
Remove the URL

This is a "fix" because now the jobs are labeled as successful. Nevertheless, removing the URL only avoids executing the "buggy" callback functionality and hence, it is a ticket. I marked it as high priority, because it stops workflow execution although models are executed successfully.

[imi]

Fixed in version 3.6.4.

[strauberry]

Hi, thank you for fixing this in version 3.6.4. What was the issue? What is the fix exactly? Thank you very much!

[imi]

Some internal changes were not implemented in this function. The temporary directory of the output files were modified, and the old version is not compatible with the new one.