ruby.git/test/ruby/test_random_formatter.rb, branch v3_4_9 The Ruby Programming Language Freeze `Random::Formatter::ALPHANUMERIC` and its elements 2024-12-16T11:54:40+00:00 Nobuyoshi Nakada nobu@ruby-lang.org 2024-05-18T07:14:44+00:00 946c823ddbd2f9bd9429d7d1b229a5ba773e540f 






[ruby/securerandom] Extract `assert_uuid_v7`
2023-10-12T05:58:31+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2023-09-19T02:36:25+00:00

feac15c1f3479f7d7641480a4608f3ac5d3b2fca

https://github.com/ruby/securerandom/commit/029677584d





https://github.com/ruby/securerandom/commit/029677584d







[ruby/securerandom] Removed extra argument for build failure of ruby/ruby
2023-09-19T02:22:15+00:00

Hiroshi SHIBATA
hsbt@ruby-lang.org

2023-09-19T02:13:19+00:00

b33e9f637d2af0b1dc447e31ffd3a31e26e47b13

  https://github.com/ruby/ruby/actions/runs/6230184763/job/16909829150

https://github.com/ruby/securerandom/commit/f60582432c





  https://github.com/ruby/ruby/actions/runs/6230184763/job/16909829150

https://github.com/ruby/securerandom/commit/f60582432c







[ruby/securerandom] Add support for UUID version 7
2023-09-19T01:55:27+00:00

nick evans
nicholas.evans@gmail.com

2023-06-29T22:39:29+00:00

dfb2b4cbc9aa5edc315e210bf6bfd92fcf6e45de

Although the specification for UUIDv7 is still in draft, the UUIDv7
algorithm has been relatively stable as it progresses to completion.

Version 7 UUIDs can be very useful, because they are lexographically
sortable, which can improve e.g: database index locality.  See section
6.10 of the draft specification for further explanation:

  https://datatracker.ietf.org/doc/draft-ietf-uuidrev-rfc4122bis/

The specification allows up to 12 bits of extra timestamp precision, to
make UUID generation closer to monotonically increasing.  This provides
between 1ms and ~240ns of timestamp precision.  At the cost of some code
complexity and a small performance penalty, a kwarg may specify any
arbitrary precision between 0 and 12 extra bits.  Any stronger
guarantees of monotonicity have considerably larger tradeoffs, so
nothing more is implemented.  This limitation is documented.

Ruby issue: https://bugs.ruby-lang.org/issues/19735

https://github.com/ruby/securerandom/commit/34ed1a2ec3





Although the specification for UUIDv7 is still in draft, the UUIDv7
algorithm has been relatively stable as it progresses to completion.

Version 7 UUIDs can be very useful, because they are lexographically
sortable, which can improve e.g: database index locality.  See section
6.10 of the draft specification for further explanation:

  https://datatracker.ietf.org/doc/draft-ietf-uuidrev-rfc4122bis/

The specification allows up to 12 bits of extra timestamp precision, to
make UUID generation closer to monotonically increasing.  This provides
between 1ms and ~240ns of timestamp precision.  At the cost of some code
complexity and a small performance penalty, a kwarg may specify any
arbitrary precision between 0 and 12 extra bits.  Any stronger
guarantees of monotonicity have considerably larger tradeoffs, so
nothing more is implemented.  This limitation is documented.

Ruby issue: https://bugs.ruby-lang.org/issues/19735

https://github.com/ruby/securerandom/commit/34ed1a2ec3







[Feature #18183] Add `chars:` option to `Random#alphanumeric`
2023-08-29T01:56:56+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2023-08-29T01:56:56+00:00

7e5c662a6f2e8435f8103bc16185bed6759cc557












[ruby/securerandom] Use String#unpack1
2021-12-14T02:59:22+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2021-12-13T15:55:02+00:00

900e0c8c39fe3df72d7ce451e01c1add7b6f1647

https://github.com/ruby/securerandom/commit/5460a18c35





https://github.com/ruby/securerandom/commit/5460a18c35







[ruby/securerandom] Split Random::Formatter from SecureRandom [Feature #18190]
2021-12-09T11:26:44+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2021-12-05T12:53:35+00:00

12a0a89e22fbc312e4a95a7749bc153532daa855

https://github.com/ruby/securerandom/commit/1e57277b9e





https://github.com/ruby/securerandom/commit/1e57277b9e