Displaying 2 results from an estimated 2 matches for "testrecording".
2005 Jan 30
1
Monitor calls timeout
...ter 10 seconds.
Here's what the console tells me:
-- Attempting call on Zap/4/442,55 for s@record:1 (Retry 1)
> Channel Zap/4-1 was answered.
-- Executing Answer("Zap/4-1", "") in new stack
-- Executing SetVar("Zap/4-1",
"RECORDFILENAME=testrecording-s-20050131-102716") in new stack
-- Executing Monitor("Zap/4-1", "wav||m") in new stack
[all good so far]
Jan 31 10:27:26 WARNING[27937712]: pbx.c:1977 ast_pbx_run: Timeout,
but no rule 't' in context 'record'
-- Hungup 'Zap/4-1'
[okay, so...
2012 Jun 21
6
where do I report this DateTime bug?
I have isolated what appears to be a bug in the Rails extensions to
DateTime, but I don''t know where to report it.
I have a standalone file to demonstrate the bug, but the punch line is
that this code:
TestRecord.create!(:f_datetime => (expected = DateTime.jd(2000000)))
found = TestRecord.first.f_datetime
puts("expected == found => #{expected == found}")