Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @grunch ,
first idea for fix the issue #264 .
Modified a bit this function
pubkey_event_can_solve
In this way if a
solver
takes first a dispute we have to check that dispute is inInitiated
state, which (imo) is the only one a solver can take.While an admin can overtake also
InProgress
state, so now he will become the solver and other solvers cannot take the dispute again.You will see that I removed also
pubkey_event_can_solve
fromadmin_cancel.rs
andadmin_settle.rs
because ( still imo ) they are redundat because ofis_assigned_solver
that is responsible to check if the pubkey of message is the solver.If, for example, an admin overtake a solver dispute he will be the new solver so the check below should be enough.
Let me know!