[#90865] [Ruby trunk Bug#15499] Breaking behavior on ruby 2.6: rb_thread_call_without_gvl doesn't invoke unblock_function when used on the main thread — apolcyn@...
Issue #15499 has been reported by apolcyn (alex polcyn).
3 messages
2019/01/03
[#90877] [Ruby trunk Bug#15499] Breaking behavior on ruby 2.6: rb_thread_call_without_gvl doesn't invoke unblock_function when used on the main thread — apolcyn@...
Issue #15499 has been updated by apolcyn (alex polcyn).
3 messages
2019/01/03
[#90895] Re: [ruby-alerts:11680] failure alert on trunk-mjit@silicon-docker (NG (r66707)) — Eric Wong <normalperson@...>
ko1c-failure@atdot.net wrote:
4 messages
2019/01/05
[#90896] Re: [ruby-alerts:11680] failure alert on trunk-mjit@silicon-docker (NG (r66707))
— Takashi Kokubun <takashikkbn@...>
2019/01/05
Thanks to explain that.
[#91200] [Ruby trunk Feature#15553] Addrinfo.getaddrinfo supports timeout — glass.saga@...
Issue #15553 has been reported by Glass_saga (Masaki Matsushita).
4 messages
2019/01/21
[#91289] Re: [Ruby trunk Feature#15553] Addrinfo.getaddrinfo supports timeout
— Eric Wong <normalperson@...>
2019/01/26
glass.saga@gmail.com wrote:
[ruby-core:91082] [Ruby trunk Misc#15534] Is there reliable way to check for new Ruby releases?
From:
v.ondruch@...
Date:
2019-01-14 14:34:40 UTC
List:
ruby-core #91082
Issue #15534 has been reported by vo.x (Vit Ondruch). ---------------------------------------- Misc #15534: Is there reliable way to check for new Ruby releases? https://bugs.ruby-lang.org/issues/15534 * Author: vo.x (Vit Ondruch) * Status: Open * Priority: Normal * Assignee: ---------------------------------------- In Fedora, we are using https://release-monitoring.org/ to check for packages updates. Unfortunately, the content of https://cache.ruby-lang.org/pub/ruby/ is a bit inconsistent which makes this service unuseful. If I open the page, there are listed a lot of packages, but for some reason, the later 2.6 releases are missing. There is a "stable" folder, but it contains just Ruby 2.3, which is quite stable, but I would expect there something more recent. There is a "binaries" folder, which contains some ancient binaries. There is also index.txt, which looks to be promising, but I am not sure. So I wonder: 1. What is the most reliable version information 2. If it would be possible to clean up the repository 3. and make sure the information is consistent -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>