Bug #12649

DateTime method calls hang

Added by ohler (Peter Ohler) over 3 years ago. Updated 6 months ago.

Third Party's Issue
Target version:


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.

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) over 3 years ago

  • Assignee set to nobu (Nobuyoshi Nakada)
  • Status changed from Open to Assigned

Updated by jeremyevans0 (Jeremy Evans) 6 months ago

  • Status changed from Assigned to Third Party's Issue

Also available in: Atom PDF