Bug #1895 [Csd->Opn]: pear search <term>

Edit report at http://pear.php.net/bugs/bug.php?id=1895&edit=1 ID: 1895 User updated by: danielc at analysisandsolutions dot com Reported By: danielc at analysisandsolutions dot com -Status: Closed +Status: Open Type: Bug Package: Web Site Operating System: Irrelevant PHP Version: Irrelevant Assigned To: pajoye New Comment: Pierre: For now, putting the issue of why the cache is becoming corrupted, it would be very helpful if you could please debug why PEAR_Remote::call(), or it's sub-calls, is returning data other than an array rather than raising an error. Perhaps they have raised an error, but that error isn't being properly cought. The goal being to get a real, helpful, error message to be displayed rather than the irrelevant "invalid argument supplied for foreach." Thanks. Previous Comments: ------------------------------------------------------------------------ [2004-07-17 10:28:01] pierre at dotgeek dot org Fixed. The cache was broken for an unknown reason. Did you guys change something recently? If you get this problem again, please reopen this bug. --Pierre ------------------------------------------------------------------------ [2004-07-16 17:02:06] danielc at analysisandsolutions dot com Description: ------------ Matthew Weier O'Phinney posted on pear-general, and then Norbert Mocsnik forwarded to pear-dev the following issue. > I get the following when I run a 'pear search xxx': > > Warning: Invalid argument supplied for foreach() in Remote.php on line 263 > no packages found Line 263 is part of the the doSearch() method in pear/PEAR/Command/Remote.php. That line is foreach ($available as $name => $info) { $available comes from: $r = new PEAR_Remote($this->config); $available = $r->call('package.listAll', true, false); call() then invokes XML RPC and caching, passing 'package.listAll' to a new XML_RPC_Message object that then gets passed to XML_RPC_Client::send(). Something along the way is returning bad info for some reason. Then the error isn't being handled properly before being passed to the foreach. Both issues need addressing. I'll leave resolving these matters up to the folks who are more familliar with the inner workings of all this. ------------------------------------------------------------------------ -- Edit this bug report at http://pear.php.net/bugs/bug.php?id=1895&edit=1