Skip to content
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

Potential unclear usage of notify and notify_backtrack #54

Open
ImkoMarijnissen opened this issue Sep 23, 2024 · 0 comments
Open

Potential unclear usage of notify and notify_backtrack #54

ImkoMarijnissen opened this issue Sep 23, 2024 · 0 comments
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@ImkoMarijnissen
Copy link
Contributor

Currently, we only notify of backtrack events when the forward event has occurred; however, this can lead to the case where a propagator detects that a task is fixed (since it is fixed in the context provided to the method) and makes some adjustments to its datastructures expecting to receive a notification that it was unfixed while this event never arrive since it never got the forward event.

A decision should be made as to whether we want to inform the user more explicitly of this fact or whether we always want to process all domain events even upon conflicts

@ImkoMarijnissen ImkoMarijnissen added bug Something isn't working documentation Improvements or additions to documentation labels Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant