[imp] Search "entire message" member function fetch() on a non-object

Thu Jun 12 22:10:34 UTC 2014

Quoting Samuel Wolf <samuel at sheepflock.de>:

> Zitat von Hiromi Kimura <hiromi at tac.tsukuba.ac.jp>:
>
>> From: Michael M Slusarz <slusarz at horde.org>
>> Subject: Re: [imp] Search "entire message" member function fetch()  
>> on a non-object
>> Date: Thu, 12 Jun 2014 01:21:50 -0600
>>
>>> Quoting Samuel Wolf <samuel at sheepflock.de>:
>>>
>>>> Zitat von Michael M Slusarz <slusarz at horde.org>:
>>>>
>>>>> Quoting Samuel Wolf <samuel at sheepflock.de>:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> at the moment I use IMP-6.2.0beta1* with Horde-5.2.0beta2 and
>>>>>> Horde_Core-2.12.0beta2 since there are some bugs which affect me in
>>>>>> IMP-6.2.0beta2.
>>>>>>
>>>>>> One of my user can search in the INBOX with "entire message", get the
>>>>>> search result and can open the message in the preview mode.
>>>>>> Same user can search in the "Sent" folder with "entire message", get
>>>>>> the search result but after select a message or double click on it
>>>>>> Horde show "Error when communicating with the server.".
>>>>>>
>>>>>> Horde.log:
>>>>>> 2014-06-07T13:53:02+00:00 EMERG: HORDE [imp] Call to a member function
>>>>>> fetch() on a non-object [pid 17325 on line 1616 of
>>>>>> "/var/www/http/horde/imp/lib/Contents.php"]
>>>>>>
>>>>>> POST https://example.com/horde/services/ajax.php/imp/showMessage
>>>>>> [HTTP/1.0 500 Internal Server Error 297ms]
>>>>>> "onFailure" {request: Object, transport: XMLHttpRequest, readyState:
>>>>>> 4, status: 500, statusText: "Internal Server Error", responseText:
>>>>>> "<html>
>>>>>> <head><title>Horde :: Fatal Error</title></head>
>>>>>> <body style="background:#fff; color:#000"><h1>A fatal error has
>>>>>> occurred</h1><h3>Call to a member function fetch() on a
>>>>>> non-object</h3><h3>Details have been logged for the
>>>>>> administrator.</h3></body></html>", headerJSON: null, responseXML:
>>>>>> null, responseJSON: null}
>>>>>>
>>>>>> It works sometimes in sent, but do not found the logic when it works
>>>>>> an when not. :(
>>>>>>
>>>>>> Any ideas?
>>>>>
>>>>> Absolutely no clue.  There are only two outcomes to calling fetch() -
>>>>> it returns a Results object or it throws an Exception.  Neither could
>>>>> produce this error message.  You will need to debug locally.
>>>>
>>>> Michael, help this to track the issue down?
>>>
>>> Maybe it's this (?)
>>>
>>> https://github.com/horde/horde/commit/531dd6eb2ae6a71ed627fe92807a494c4a841d5f
>>
>> Sorry, I installed from Git and got same result.
>>
>> I revert some old tar-ball of installation which installed from Git.
>> 8th April (GMT+9) version is OK,
>> 10th April version and later have this issue.
>
> Is it possible for you to find the commit which cause the issue?

No.  First, because no developer can reproduce.  And second: nothing  
changed between April 8 and April 10 in imp that would have caused  
this behavior (that's the only debugging information we have been  
given):

slusarz at bigworm % git log --no-merges --after={2014-04-08}  
--before={2014-04-11}  .
commit fc59746b736abbd51d22b06c40a920edae4fa33c
Author: Jan Schneider <jan at horde.org>
Date:   Wed Apr 9 19:32:06 2014 +0200

     Set signature when toggling editor even if not converting text.

commit ea9821dcdb885f2a6bd5cbc5299521b6a9a6c311
Author: Jan Schneider <jan at horde.org>
Date:   Wed Apr 9 19:31:33 2014 +0200

     this.rte was already used for the signature editor.

     Moving everything to ImpComposeBase made both editors referencing the same
     instance, causing all kind of broken behavior.

commit 411fcb9d888259dddefe653828e29073fc3fcb53
Author: Jan Schneider <jan at horde.org>
Date:   Tue Apr 8 18:56:44 2014 +0200

     Prepare alpha releases.

commit 44b1c13a2eb5acc540a38e4619ebc27c6fd35028
Author: Jan Schneider <jan at horde.org>
Date:   Thu Apr 3 18:27:26 2014 +0200

     Add instructions for upgrading binaries and pre-releases.

commit 9e5ec5157bc8d0b95dc9990c86a353d8b0ee6c32
Author: Jan Schneider <jan at horde.org>
Date:   Tue Apr 8 18:28:43 2014 +0200

     Not only display.

(For the record, nothing changed in Horde_Imap_Client between these  
dates either.)

michael

___________________________________
Michael Slusarz [slusarz at horde.org]