avivijay19 commented on PR #6176: URL: https://github.com/apache/fineract/pull/6176#issuecomment-5181857122
Agreed, closing this. You're right that the new transaction decouples the date write from the job status — and worse, a rerun after a false FAILED would increase the date twice, which is a worse outcome than the duplicate key it was avoiding. The only real symptom was `SchedulerJobsTest.testTriggeringManualExecutionOfAllSchedulerJobs` executing every job in parallel, so the two date jobs raced to create the initial row. Fixing it there instead. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
