You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 2, 2024. It is now read-only.
When a job fails, the method Job._unlock_edit_on_outputs is called on the failed job and on all jobs to abandon. This method triggers the execution of the method DataNode.unlock_edit on all the outputs, which updates the last_edit_date.
Consequently, the 'last_edit_date' is wrong on the output data nodes.
This is a blocking issue in the specific case where a data node has its 'last_edit_date' updated while it has never been written. In this case, Taipy can try to read it, leading to an error thrown.
Requires a hotfix on release 2.0!
Requires a release note update on 2.0.4.
The text was updated successfully, but these errors were encountered:
* fix#366 update last_edit_date when a job fails or is abandoned
* change version to 2.0.4
jrobinAV
changed the title
Do not update last_edit_date for abandoned and failed jobs
BUG-Do not update last_edit_date for abandoned and failed jobs
Nov 24, 2022
When a job fails, the method
Job._unlock_edit_on_outputs
is called on the failed job and on all jobs to abandon. This method triggers the execution of the methodDataNode.unlock_edit
on all the outputs, which updates thelast_edit_date
.Consequently, the 'last_edit_date' is wrong on the output data nodes.
This is a blocking issue in the specific case where a data node has its 'last_edit_date' updated while it has never been written. In this case, Taipy can try to read it, leading to an error thrown.
Requires a hotfix on release 2.0!
Requires a release note update on 2.0.4.
The text was updated successfully, but these errors were encountered: