Open
0 of 2 issues completed
Description
KSUID seems to have second precision and not ms/ns precision because of which id generation is shuffled for the same minute.
TS : 2024-11-04T18:02:07.026Z - id : 2oOayA9mfiFdFG4M1brPu3rfO0X
TS: 2024-11-04T18:02:07.025Z. - id: 2oOayC2SOU84wN95sZOIfMDMLDJ
ksuid -f inspect 2oOayA9mfiFdFG4M1brPu3rfO0X
REPRESENTATION:
String: 2oOayA9mfiFdFG4M1brPu3rfO0X
Raw: 13B6BE1F69D0C929FFA4932C944BA846902809A9
COMPONENTS:
Time: 2024-11-04 23:32:07 +0530 IST
Timestamp: 330743327
Payload: 69D0C929FFA4932C944BA846902809A9
ksuid -f inspect 2oOayC2SOU84wN95sZOIfMDMLDJ
REPRESENTATION:
String: 2oOayC2SOU84wN95sZOIfMDMLDJ
Raw: 13B6BE1FA7A57487AAADD3F10E826FDD31B5B12D
COMPONENTS:
Time: 2024-11-04 23:32:07 +0530 IST
Timestamp: 330743327
Payload: A7A57487AAADD3F10E826FDD31B5B12D
The way to solve this will be ms/ns level presion in ksuid.
cc @srikanthccv