[#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
[#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).
ko1@atdot.net wrote:
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
QXMgSSB0b2xkIHlvdSwgYG1ha2UgaW5zdGFsbGAgaXMgbmVlZGVkIHRvIG1ha2UgUnVieSB3b3Jr
T25lIG1vcmUgcmVhc29uIGZvciBodHRwczovL2J1Z3MucnVieS1sYW5nLm9yZy9pc3N1ZXMvMTM2
[#87986] [Ruby trunk Feature#14915] Deprecate String#crypt, move implementation to string/crypt — mame@...
Issue #14915 has been updated by mame (Yusuke Endoh).
mame@ruby-lang.org wrote:
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).
[#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).
[#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).
[#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).
[#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).
takashikkbn@gmail.com wrote:
> yet, sky3 had a failure at
> http://ci.rvm.jp/results/trunk@P895/1173951
> > http://ci.rvm.jp/results/trunk@P895/1173951
[ruby-core:88061] Re: [Ruby trunk Feature#14915] Deprecate String#crypt, move implementation to string/crypt
merch-redmine@jeremyevans.net wrote: > shyouhei (Shyouhei Urabe) wrote: > > - Basic authentication itself does not require DES. It is an > > implementation detail. You can safely migrate to another > > hash function at will. Ruby's openssl library has for > > instance OpenSSL::KDF.scrypt(). > > Note that OpenSSL::KDF.scrypt is only defined if the OpenSSL > library defines EVP_PBE_scrypt, so it isn't always available. > I believe this was added in OpenSSL 1.1.0, and it isn't > currently available in LibreSSL. OpenSSL::KDF.pbkdf2_hmac is > always defined, so that could be used as long as the openssl > extension can be required. > > Personally, I think it's best to punt and require the user > provide implementations for creating a password hash and > checking the password hash via two callable options (e.g. > :create_password_hash and :check_password_hash). Can you provide pre-defined, accepted-as-secure implementations of these which we can recommend for common use cases which would be compatible with other webservers? I'd rather not introduce/recommend hashes which are incompatible with other webservers, but two-way compatibility with existing servers is a good thing. It could optionally recommend/use 3rd-party gem if available (e.g. 'bcrypt'), or the bundled 'openssl' ext. > That way the user can determine which password hash format > they want to use, and it doesn't tie Webrick to one particular > hash implementation. If that is considered acceptable I can > work on a patch for Webrick that keeps the current default > behavior with a deprecation warning if the callable options > are not provided. That seems reasonable, but I want to avoid situations where users cargo-cult blocks of code into the config they don't understand. They could get stuck with an option which is eventually found insecure and we'd have no way of warning them. Thanks. Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>