You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the case where more than 4095 iterations have happened within the same millisecond and the sequence number is reset to 0, while the program does wait for the time to move onto the next millisecond the current time variable is not updated with the new time. This means that the 0th id in the sequence and the new 0th id would be the same if the 4095 limit was reached on the same millisecond. In this case one millisecond should be added to the time and bTime variables. I know this is a very unlikely event but I thought I should still mention it :)
The text was updated successfully, but these errors were encountered:
In the case where more than 4095 iterations have happened within the same millisecond and the sequence number is reset to 0, while the program does wait for the time to move onto the next millisecond the current time variable is not updated with the new time. This means that the 0th id in the sequence and the new 0th id would be the same if the 4095 limit was reached on the same millisecond. In this case one millisecond should be added to the time and bTime variables. I know this is a very unlikely event but I thought I should still mention it :)
The text was updated successfully, but these errors were encountered: