Describe the bug
validUntil is null which makes expiration timestamp identical with creation date of C2D job when starting a new c2d job, meaning that the running algorithm will stop abruptly due to timeout its execution without reaching the its end properly because maxDurationJob timestamp is not taken in account when computing expiration timestamp.
Expected behavior
To respect configured maxJobDuration.
Screenshots
dateCreated: '1743227446.917',
dateFinished: null,
status: 0,
statusText: 'Job started',
results: null,
inputDID: null,
algoDID: null,
agreementId: null,
expireTimestamp: 1743227446.917
Running algorithm phase logs:
running, need to stop it?
timeNow: 1743227458.119 , Expiry: 1743227446.917
Additional context
Ran face-detection.py algorithm with vscode-extension, locally it works but it takes 3 mins to return the output video and using ocean-node c2d it does not finish generating the output video.
Describe the bug
validUntilis null which makes expiration timestamp identical with creation date of C2D job when starting a new c2d job, meaning that the running algorithm will stop abruptly due to timeout its execution without reaching the its end properly becausemaxDurationJobtimestamp is not taken in account when computing expiration timestamp.Expected behavior
To respect configured maxJobDuration.
Screenshots
Running algorithmphase logs:Additional context
Ran face-detection.py algorithm with vscode-extension, locally it works but it takes 3 mins to return the output video and using ocean-node c2d it does not finish generating the output video.