Tickets :: [#9424] Registry losing cached interfaces information

6.0.0-beta1

7/6/25

Summary	Registry losing cached interfaces information
Queue	Horde Framework Packages
Queue Version	Git master
Type	Bug
State	Resolved
Priority	3. High
Owners	jan (at) horde (dot) org, slusarz (at) horde (dot) org
Requester	jan (at) horde (dot) org
Created	12/02/2010 (5330 days ago)
Due
Updated	12/20/2010 (5312 days ago)
Assigned	12/17/2010 (5315 days ago)
Resolved	12/20/2010 (5312 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

12/20/2010 07:48:57 PM	Jan Schneider	Comment #9 State ⇒ Resolved	Reply to this comment
w00t!!1!

12/20/2010 07:16:57 PM	Michael Slusarz	Comment #8	Reply to this comment
Think I figured it out... I could reproduce if I changed the language in my browser. The issue is that when we change languages, we flushed the registry cache. Previously there was a long-standing bug where we would flush the cache but we wouldn't rebuild the current registry object. Thus, things like the application names and other translated items within the cache weren't updateduntil the next page load. I partially fixed this, but made the mistake of not correctly marking the api list as unset. Thus, after clearing the cache, the registry would not rebuild the api list because it was marked as already built. This has been fixed.

12/20/2010 07:11:49 PM	Git Commit	Comment #7	Reply to this comment
Changes have been made in Git for this ticket: ~~Bug #9424~~: Need to unset apis variable - or else it won't be rebuilt http://git.horde.org/horde-git/-/commit/7fd5d34ce9e01a6ccc027131894b18b3c0a813aa

12/17/2010 08:52:50 PM	Michael Slusarz	Comment #6 State ⇒ Feedback Assigned to Jan Schneider	Reply to this comment
Maybe this helps: http://lists.horde.org/archives/commits/2010-December/005893.html Retracting other statements I made in this ticket - not sure it is an auth thing because api cache is stored in the same data element as interfaces cache - if one is set but not the other, something weird is going on. Also, we DO need the md5 hash in the session because all cached elements may not be the same for all users. Adding Jan as owner because he can reproduce (I can't).

12/13/2010 07:40:49 PM	Michael Slusarz	Comment #5	Reply to this comment
My guess is that it has something to do with transparent auth. But the registry caching code needs to be rewritten anyway - the md5 session storage code doesn't make a lot of sense (I think it was intended to prevent registry changes from affecting current sessions, but it doesn't work reliably 100% of the time so it is useless).

12/13/2010 07:24:38 PM	Michael Slusarz	Summary ⇒ Registry losing cached interfaces information

12/13/2010 07:24:01 PM	Michael Slusarz	Comment #4 Summary ⇒ Registry losing cached interfaces informationIW,	Reply to this comment
FWIW, I have never seen this. bugs.horde.org works fine for me.

12/13/2010 04:10:40 PM	jan (at) horde (dot) org	Comment #3	Reply to this comment
Bump. This keeps me from working on any bugs at the moment.

12/08/2010 01:34:08 PM	rsalmon (at) mbpgroup (dot) com	Comment #2	Reply to this comment
Using Firefox, I've noticed that if I clear cache and cookies then open URL like http://bugs.horde.org/ticket/9424, I always get the fatal error. Reloading the page works fine. Hope this helps.

12/02/2010 02:39:51 PM	Jan Schneider	Comment #1 State ⇒ Assigned Patch ⇒ No Milestone ⇒ Assigned to Michael Slusarz Queue ⇒ Horde Framework Packages Summary ⇒ Registry losing cached interfaces information Type ⇒ Bug Priority ⇒ 3. High	Reply to this comment
As can be seen on bugs.horde.org, the registry under certain conditions loses the $this->_cache['interfaces'] entry, resulting in "The method "tickets/getQueueDetails" is not defined in the Horde Registry." fatal errors. The entry is properly populated, but when using call() of the registry later, the entry is empty again. the 'api' entry always keeps populated.