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

Transactional conclusion #20

Open
matthiasgeihs opened this issue Aug 17, 2022 · 0 comments
Open

Transactional conclusion #20

matthiasgeihs opened this issue Aug 17, 2022 · 0 comments

Comments

@matthiasgeihs
Copy link
Contributor

Currently, the conclude functionality has two writes:

  1. Set the outcome.
  2. Conclude the registered state.

Problem: There is a risk that the first transaction goes through, while the second fails. In this case we might end up in an inconsistent state.

We need to investigate further whether the current solution is problematic and if so, how to resolve the situation. Maybe using the transaction decorator might be a solution, as pointed out here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant