Account for asynchrony between builders and guarantors on work package submission #2
Description
The asynchrony between a builder submitting a work package to each guarantor in parallel may cause the package to be simultaneously refined by the current and the next set of guarantors.
This happens on epoch/rotation change that occurs during package submission when at least one guarantor is assigned to the same core as in previous epoch/rotation. When the package is submitted to such a guarantor, it is then shared by this guarantor with other guarantors from the set, resulting in the package being refined by the two overlapping sets of guarantors.
As pointed out by Dave a misbehaving builder might do the same on purpose.
Possible solutions:
- Send slot/rotation/epoch together with the package. This would resolve the issue for well-behaving builders.
- Establish some kind of a communication channel between the current and the next set of guarantors to prevent refining the same package by both sets. This would resolve the issue for misbehaving builders as well.