-
Notifications
You must be signed in to change notification settings - Fork 186
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
Process CLOCK_MONOTONIC_RAW_APPROX, CLOCK_UPTIME_RAW, and CLOCK_UPTIME_RAW_APPROX constants are not supported #1480
Comments
I'm curious, which library uses this constant? |
No one in my case, I just saw this in Ruby 2.4 NEWS. So I just was curious to try it 😇 |
For Linux we need to implement
|
Fix on the way. |
Sorry this was fixed ages ago, forgot to close it. |
This doesn't seem fixed or fixed still? On latest truffleruby:
|
It was fixed but regressed, unfortunately the test guard was written incorrectly and so missed the regression (I'll fix that). @nickh-stripe Do you need |
I've got a fix. The trade-off is it will also define these clocks as Process constants on older Linux, and using them with |
Thanks, just some existing code was using it, I don't know enough about why to say whether it could be substituted, just thought reporting it for a easy fix might be beneficial to all 👍 thanks for the quick turnaround. |
…_ALARM * Giving a non-existing clock to clock_gettime() raises Errno::EINVAL, which seems fairly harmless. * Fixes oracle#1480
This is specific for macOS and it was introduced in Ruby 2.4. See https://github.com/ruby/ruby/blob/v2_4_0/NEWS
To reproduce (only on macOS, I guess):
Error:
The text was updated successfully, but these errors were encountered: