Signing Page - Sigit Not Updated With 2+ Signers #168
Labels
No Label
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sigit/sigit.io#168
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In my recent test, when there are more than 3 signers, and the creator is not the first signer, the state of the Sigit was not updated from the 2nd to the 3rd signer. It means that the 3rd Signer is not able to complete signing, as it still shows that we are waiting for the 2nd Signature.
While the root cause needs to be investigate, a potential safeguard mechanism could be to add a capability for any signer to "synchronise" or "check for updates" of the state of the sigit.