View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000076 | Timekoin Server | General Issue | public | 2021-08-14 14:16 | 2021-08-16 23:55 |
Reporter | KnightMB | Assigned To | KnightMB | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Product Version | 4.13 | ||||
Target Version | 4.15 | Fixed in Version | 4.15 | ||
Summary | 0000076: Creating a new Easy Key at the exact same time as a Peer Election results in failure | ||||
Description | If 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 Reproduce | Wait until the same transaction cycle as the Peer election is suppose to finish and then create a new Easy Key. | ||||
Additional Information | Basically a logic timing issue. | ||||
Tags | No tags attached. | ||||
|
I was able to confirm it by creating a new Easy Key at the same time that a Peer was to be elected. |
|
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. |
|
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. |
|
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. |
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 |