View Issue Details

IDProjectCategoryView StatusLast Update
0000076Timekoin ServerGeneral Issuepublic2021-08-16 23:55
ReporterKnightMB Assigned ToKnightMB  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Version4.13 
Target Version4.15Fixed in Version4.15 
Summary0000076: Creating a new Easy Key at the exact same time as a Peer Election results in failure
DescriptionIf you create an Easy Key during the same cycle as a Peer Election is suppose to finish, it will fail because the new Peer that was just elected was not included in the round of payments to all the servers.
Steps To ReproduceWait until the same transaction cycle as the Peer election is suppose to finish and then create a new Easy Key.
Additional InformationBasically a logic timing issue.
TagsNo tags attached.

Activities

KnightMB

2021-08-14 14:16

administrator   ~0000072

I was able to confirm it by creating a new Easy Key at the same time that a Peer was to be elected.

KnightMB

2021-08-14 14:17

administrator   ~0000073

Should be an easy fix, if you try to create a Easy Key at the exact same time as the Peer Election, just have it queue to wait until the next cycle when the new Peer will be in the Generation List.

KnightMB

2021-08-15 01:33

administrator   ~0000074

Just added an election check to prevent creation right before a peer election and a message to the user to wait on the creation. Having an automated system to check the election status and submit between elections is beyond the current schedule scope to get this release out for the speed benefits and more important bug fixes.

KnightMB

2021-08-16 23:55

administrator   ~0000076

Timekoin will attempt to fit an Easy Key creating transaction in before any election is suppose to finish. If it's too close to predict (especially if multiple servers are in the queue to be elected), it will return error and tell the user to wait until the election has passed to try again.

Issue History

Date Modified Username Field Change
2021-08-14 14:16 KnightMB New Issue
2021-08-14 14:16 KnightMB Status new => assigned
2021-08-14 14:16 KnightMB Assigned To => KnightMB
2021-08-14 14:16 KnightMB Status assigned => confirmed
2021-08-14 14:16 KnightMB Note Added: 0000072
2021-08-14 14:17 KnightMB Note Added: 0000073
2021-08-15 01:33 KnightMB Status confirmed => resolved
2021-08-15 01:33 KnightMB Resolution open => fixed
2021-08-15 01:33 KnightMB Fixed in Version => 4.14
2021-08-15 01:33 KnightMB Note Added: 0000074
2021-08-15 01:35 KnightMB Target Version 4.14 => 4.15
2021-08-15 01:36 KnightMB Status resolved => acknowledged
2021-08-16 23:55 KnightMB Status acknowledged => resolved
2021-08-16 23:55 KnightMB Fixed in Version 4.14 => 4.15
2021-08-16 23:55 KnightMB Note Added: 0000076