[#87773] timer thread [was Re: [ruby-alerts:7905] failure alert on trunk-asserts@silicon-docker (NG (r63844))] — Eric Wong <normalperson@...>
> test_all <main>: warning: pthread_create failed for timer: Resource temporarily unavailable, scheduling broken
3 messages
2018/07/04
[#87836] [Ruby trunk Bug#14898] test/lib/test/unit/parallel.rb: TestSocket#test_timestamp stuck sometimes — ko1@...
Issue #14898 has been reported by ko1 (Koichi Sasada).
5 messages
2018/07/06
[#87838] Re: [Ruby trunk Bug#14898] test/lib/test/unit/parallel.rb: TestSocket#test_timestamp stuck sometimes
— Eric Wong <normalperson@...>
2018/07/06
[email protected] wrote:
[#87842] Re: [Ruby trunk Bug#14898] test/lib/test/unit/parallel.rb: TestSocket#test_timestamp stuck sometimes
— Koichi Sasada <ko1@...>
2018/07/07
On 2018/07/06 18:47, Eric Wong wrote:
[#87847] undefined symbol: mjit_init_p — Leam Hall <leamhall@...>
I pulled Ruby trunk on 3 Jul and am now getting errors similar to the
10 messages
2018/07/07
[#87849] Re: undefined symbol: mjit_init_p
— Takashi Kokubun <takashikkbn@...>
2018/07/07
QXMgSSB0b2xkIHlvdSwgYG1ha2UgaW5zdGFsbGAgaXMgbmVlZGVkIHRvIG1ha2UgUnVieSB3b3Jr
[#87852] Re: undefined symbol: mjit_init_p
— Benoit Daloze <eregontp@...>
2018/07/07
T25lIG1vcmUgcmVhc29uIGZvciBodHRwczovL2J1Z3MucnVieS1sYW5nLm9yZy9pc3N1ZXMvMTM2
[#87986] [Ruby trunk Feature#14915] Deprecate String#crypt, move implementation to string/crypt — mame@...
Issue #14915 has been updated by mame (Yusuke Endoh).
5 messages
2018/07/18
[#87987] Re: [Ruby trunk Feature#14915] Deprecate String#crypt, move implementation to string/crypt
— Eric Wong <normalperson@...>
2018/07/18
[email protected] wrote:
[#88000] Re: [Ruby trunk Feature#14915] Deprecate String#crypt, move implementation to string/crypt
— "Urabe, Shyouhei" <shyouhei@...>
2018/07/19
normalperson (Eric Wong) wrote:
[#88088] [Ruby trunk Misc#14937] [PATCH] thread_pthread: lazy-spawn timer-thread only on contention — normalperson@...
Issue #14937 has been reported by normalperson (Eric Wong).
9 messages
2018/07/24
[#88104] [Ruby trunk Bug#14898] test/lib/test/unit/parallel.rb: TestSocket#test_timestamp stuck sometimes — ko1@...
Issue #14898 has been updated by ko1 (Koichi Sasada).
3 messages
2018/07/25
[#88173] [Ruby trunk Bug#14950] r64109 thread.c: move ppoll wrapper before thread_pthread.c - Windows compile failure - thread.c — Greg.mpls@...
Issue #14950 has been reported by MSP-Greg (Greg L).
3 messages
2018/07/29
[#88189] [Ruby trunk Bug#14950] r64109 thread.c: move ppoll wrapper before thread_pthread.c - Windows compile failure - thread.c — nobu@...
Issue #14950 has been updated by nobu (Nobuyoshi Nakada).
3 messages
2018/07/30
[#88199] [Ruby trunk Misc#14937] [PATCH] thread_pthread: lazy-spawn timer-thread only on contention — takashikkbn@...
Issue #14937 has been updated by k0kubun (Takashi Kokubun).
7 messages
2018/07/30
[#88213] Re: [Ruby trunk Misc#14937] [PATCH] thread_pthread: lazy-spawn timer-thread only on contention
— Eric Wong <normalperson@...>
2018/07/30
[email protected] wrote:
[#88219] Re: [Ruby trunk Misc#14937] [PATCH] thread_pthread: lazy-spawn timer-thread only on contention
— Eric Wong <normalperson@...>
2018/07/30
> yet, sky3 had a failure at
[#88306] Re: [Ruby trunk Misc#14937] [PATCH] thread_pthread: lazy-spawn timer-thread only on contention
— Eric Wong <normalperson@...>
2018/08/06
> http://ci.rvm.jp/results/trunk@P895/1173951
[#88308] Re: [Ruby trunk Misc#14937] [PATCH] thread_pthread: lazy-spawn timer-thread only on contention
— Eric Wong <normalperson@...>
2018/08/06
> > http://ci.rvm.jp/results/trunk@P895/1173951
[ruby-core:87912] [Ruby trunk Misc#11904] Why was Thread.exclusive deprecated?
From:
sepofato@...
Date:
2018-07-11 23:48:59 UTC
List:
ruby-core #87912
Issue #11904 has been updated by sepofato (sepo fato). https://www.lotterysambadtoday.com/result/ ---------------------------------------- Misc #11904: Why was Thread.exclusive deprecated? https://bugs.ruby-lang.org/issues/11904#change-72922 * Author: bascule (Tony Arcieri) * Status: Rejected * Priority: Normal * Assignee: ---------------------------------------- See: https://bugs.ruby-lang.org/projects/ruby-trunk/repository/revisions/52554 Why was Thread.exclusive deprecated? It is useful for when you're uncertain about whether the caller is multithreaded or not, and therefore cannot initialize a mutex because the mutex must be initialized in a thread-safe context where it's not possible for multiple caller threads to initialize the mutex concurrently. One use case is here: this is an idempotent native function invoked via FFI. The contract is that it can be called repeatedly, but only by one thread at a time (concurrent calls from multiple threads can potentially corrupt its internal state): https://github.com/cryptosphere/rbnacl/blob/master/lib/rbnacl.rb#L88 Thread.exclusive is useful because it provides an implicit mutex you can ensure is initialized correctly before any other threads start. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>