midnight (Sarun R)
- Login: midnight
- Registered on: 05/15/2020
- Last sign in: 08/31/2022
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 0 | 0 | 0 |
Reported issues | 1 | 3 | 4 |
Activity
06/09/2022
- 07:13 PM Ruby master Feature #18183: make SecureRandom.choose public
- In case we really can't agree on the name.
I reimplement the functionality as an independent class on a GitHub's G...
06/06/2022
- 04:45 PM Ruby master Feature #18183: make SecureRandom.choose public
- My bad for not searching the old topics.
In this module, (most of) the method name describes the output, not the p...
06/05/2022
- 10:17 AM Ruby master Feature #18817 (Rejected): SecureRandom::choose is not being exposed
- I read through [the doc of `SecureRandom`](https://ruby-doc.org/stdlib-3.1.2/libdoc/securerandom/rdoc/SecureRandom.ht...
05/24/2022
- 10:45 PM Ruby master Bug #18791: Unexpected behavior of Socket#connect_nonblock
- The document does mention the returned value of `0`, but I'm not sure if I should also check for `EISCONN` by calling...
- 10:27 PM Ruby master Bug #18791: Unexpected behavior of Socket#connect_nonblock
- @jeremyevans0
The example is overly simplified, and it does lead to confusion in practice when you put it in context...
05/20/2022
- 01:47 PM Ruby master Bug #18792: Socket.tcp throws `getaddrinfo': no implicit conversion of Hash into String
- It's the Ruby 3 things. They don't try to match method parameters for you anymore.
You have to do it explicitly:
... - 02:38 AM Ruby master Bug #18791: Unexpected behavior of Socket#connect_nonblock
- Should I treat `0` as a successful connection?
Does anyone have an insight on this?
Does anyone want me to try some...
05/19/2022
- 07:22 PM Ruby master Bug #18791 (Rejected): Unexpected behavior of Socket#connect_nonblock
- I followed an example of [Socket#connect_nonblock](https://ruby-doc.org/stdlib-3.1.2/libdoc/socket/rdoc/Socket.html#m...
02/16/2022
- 04:12 PM Ruby master Misc #18587: What was the reason behind Ruby choosing SipHash for Hash?
- I misread a point related to extra carefulness.
They don't suggest a rehash on collision, but on hash map grow; sinc... - 03:42 PM Ruby master Misc #18587 (Open): What was the reason behind Ruby choosing SipHash for Hash?
- Hello
I am digging into the history behind Ruby using SipHash for its Hash.
I found that in 2012 there were CVE-2...
Also available in: Atom