Actions
Bug #12649
closedDateTime method calls hang
Description
When ActiveSupport 5 time is required (require 'activesupport/time') the rb_funcall() function on hour, minute, second, offset, and others causes a hang. This issue gives more details.
https://github.com/ohler55/oj/issues/306#issuecomment-235400808
A work around is to define methods on the DateTime class that just call super. That gives the correct results and does not hang.
Note that calling respond_to? returns true.
The methods work as expected in IRB or a Ruby script. Somehow Active Support 5 puts DateTime objects in a state that is not consistent between Ruby calls and those made from C.
Updated by shyouhei (Shyouhei Urabe) about 8 years ago
- Status changed from Open to Assigned
- Assignee set to nobu (Nobuyoshi Nakada)
Updated by jeremyevans0 (Jeremy Evans) about 5 years ago
- Status changed from Assigned to Third Party's Issue
Actions
Like0
Like0Like0