Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Snowflakes can be non-unique #3

Open
bobcat33 opened this issue Jan 30, 2024 · 0 comments
Open

Snowflakes can be non-unique #3

bobcat33 opened this issue Jan 30, 2024 · 0 comments

Comments

@bobcat33
Copy link

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 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant