-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG- on_submission_change called twice with same status #357
Comments
Needs a blocking event queue to make event management cleaner |
* #255 add core package ref man * Apply suggestions from code review feedback from Toan Co-authored-by: Toan Quach <93168955+toan-quach@users.noreply.github.com> * remove import * from init file * remove import * from init file * remove import * from init file Co-authored-by: Toan Quach <93168955+toan-quach@users.noreply.github.com>
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 please @FlorianJacta. |
Hi @FlorianJacta @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 |
…-called_twice feature/#357 replace submission entity with submission status
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
The text was updated successfully, but these errors were encountered: