[#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
ko1@atdot.net 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
As I told you, `make install` is needed to make Ruby work. Running
[#87852] Re: undefined symbol: mjit_init_p
— Benoit Daloze <eregontp@...>
2018/07/07
One more reason for https://bugs.ruby-lang.org/issues/13620 maybe? ;)
[#87859] Re: undefined symbol: mjit_init_p
— Eric Wong <normalperson@...>
2018/07/08
Benoit Daloze <eregontp@gmail.com> wrote:
[#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
mame@ruby-lang.org 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
takashikkbn@gmail.com 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:87744] [Ruby trunk Bug#14862] Time.parse does not handle the time zone
From:
nobu@...
Date:
2018-07-02 08:54:42 UTC
List:
ruby-core #87744
Issue #14862 has been updated by nobu (Nobuyoshi Nakada).
mifrill (Aleksey Strizhak) wrote:
> but the problem is, the behavior is different for all three objects.
`Date` doesn't have time zone, and `Date#to_time` borrows the system timezone.
> They can misunderstand the time zone, but should not the behavior be the same?
`Date` is a discrete library, but `Time` is also an interface with the system time and expected to be consistent with it.
But there is no portable way to retrieve the timezone infos, except for setting the `TZ` environment variable before startup.
----------------------------------------
Bug #14862: Time.parse does not handle the time zone
https://bugs.ruby-lang.org/issues/14862#change-72766
* Author: mifrill (Aleksey Strizhak)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.5.0p0 (2017-12-25 revision 61468) [x86_64-linux]
* Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN
----------------------------------------
First I would like to thank you for your work, thank you
The point is:
```
Time.parse("Ends from 28 Jun 2018 12:00 BST").zone
"MSK"
DateTime.parse("Ends from 28 Jun 2018 12:00 BST").zone
"+01:00"
```
--
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>