Closed FlorianJacta closed 7 months ago
Needs a blocking event queue to make event management cleaner
IS it a duplicate or the ticket #475 ?
Yes, it is a duplicate. I guess I wanted it to be solved, or my memory is fading. Do I close the other issue?
Yes, it is a duplicate. I guess I wanted it to be solved, or my memory is fading. Do I close the other issue?
YEs please @FlorianJacta.
Hi @FlorianJacta I was able to reproduce it with 3.0 but not with 3.1dev. I think the issue has been fixed!
@jrobinAV @FredLL-Avaiga I believe no fixes need to be made, but will make some changes to make some of the conditions correct. However, I must note that the on_submission_change doesn't run on development mode but does run in standalone mode, which is to be expected I think
I don't understand why it runs in one mode and not in another one ?
because in development mode, after submitting the scenario, it will run it immediately without stopping until finished. Meaning the submission entity has complete status when we're creating the _SubmissionDetails. No status change will happen after that and so the function was not called as it depends on the change in status of the job (previously, now it's submission status)
that would need to be documented Or better find a workaround to make it work in dev mode
Issue
The callback is called twice with the same status.
How to replicate
Run this code and see that two notifications are emitted.
Environment
Taipy 3.0