László GÖRÖG

``` # dpkg --print-architecture arm64 ``` But the build starts with the following: ``` # git push dokku main:master Pseudo-terminal will not be allocated because stdin is not a terminal....

``` $ docker run --rm -v /abs/app/path:/tmp/app gliderlabs/herokuish /bin/herokuish test ``` Command seem to work correctly on arm64. Output: https://gist.github.com/nerg4l/bce69372d17cb50a940285bd851d4c8f

Could you clarify for me what does "variable subsecond encoding up to nanoseconds using floating point math and fractions" and "variable subsecond encoding up to nanoseconds using integers to represent...

Thanks for the clarification. I don't think it makes sense to create `UUIDv6` and `UUIDv6ε`. Instead of pleasing everyone we should have a clear decision on which one to have....

I looked more into this and found two things which should be taken into consideration. I'm not sure if it is relevant in case of extending the RFC but ITU...

I wouldn't go as far as changing the position of the version bit. It would be better to keep the compatibility with libraries implementing RFC4122. Sure cutting nanoseconds in three...

@kyzer-davis I really like the idea of UUIDv1ε because UUIDv6 in draft 01 is almost the same as UUIDv1 with different byte order. On the other hand, I don't quite...

What do you think about having a fixed length `subsec_seq` value? The base for it would be UUIDv7 with 30 bit nsec. ``` 0 1 2 3 0 1 2...

Continuing on the idea of `subsec_seq` the sequence could have an integer limit instead of bit limit. This would mean instead of bitwise `|` a simple addition would be used...

What if a 64 bit integer is used for nanosecond time whit a `1024 * precision` sequence? The structure would look like this: ``` 0 1 2 3 0 1...