Closed
Bug 596771
Opened 15 years ago
Closed 15 years ago
Search by GUID sometimes returns no results
Categories
(addons.mozilla.org Graveyard :: API, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
5.12.2
People
(Reporter: mossop, Assigned: davedash)
References
Details
The search by GUID support added in bug 581635 seems to be intermittent. The original implementation in bug 410277 claims that we can search by multiple GUIDs so we are doing so.
The following URL works and returns both add-ons:
https://services.addons.mozilla.org/en-US/firefox/api/1.5/search/guid:inspector%40mozilla.org,personas@christopher.beard
The following URL works but only returns one add-on:
https://services.addons.mozilla.org/en-US/firefox/api/1.5/search/guid:inspector%40mozilla.org,silvermelxt%40pardal.de
The following URL returns no add-ons despite one of them having been included in the previous two cases:
https://services.addons.mozilla.org/en-US/firefox/api/1.5/search/guid:inspector%40mozilla.org,silvermelxt%40pardal.de,CrystalFox_Qute%40BigRedBrent,%7B5A170DD3-63CA-4c58-93B7-DE9FF536C2FF%7D,%7B972ce4c6-7e08-4474-a285-3208198ce6fd%7D,%7B83bfadf9-a42c-0d4f-b403-08f8897f2399%7D,%7B910c29d3-bd14-4947-ac0c-4b06e0c0b20c%7D,%7Bfa1b5a4a-0955-df41-b494-d13e876b35a7%7D
Reporter | ||
Comment 1•15 years ago
|
||
This basically blocks metadata retrieval for a number of users, can we figure out what is going on here?
blocking2.0: --- → betaN+
Updated•15 years ago
|
Target Milestone: --- → 5.12.2
Assignee | ||
Updated•15 years ago
|
Assignee: nobody → dd
Assignee | ||
Comment 2•15 years ago
|
||
In the second example:
silvermelxt%40pardal.de
There is nothing with that as a GUID, just silvermel@pardal.de.
The latter example, I have a fix for that I'll land soon. The _ was an acceptable character for the guid.
Mossop, do you have that ginormous regexp for acceptable guid characters?
Reporter | ||
Comment 3•15 years ago
|
||
(In reply to comment #2)
> In the second example:
>
> silvermelxt%40pardal.de
>
> There is nothing with that as a GUID, just silvermel@pardal.de.
This is an interesting case, that add-on is a part of a multi-package add-on. I guess we won't be able to pull metadata for such cases.
> The latter example, I have a fix for that I'll land soon. The _ was an
> acceptable character for the guid.
>
> Mossop, do you have that ginormous regexp for acceptable guid characters?
This is the regexp we test IDs against: http://mxr.mozilla.org/mozilla-central/source/toolkit/mozapps/extensions/XPIProvider.jsm#151
Assignee | ||
Comment 4•15 years ago
|
||
I know nothing of multi-package add-ons... but my guess is we aren't storing them in AMO, and therefore I can't index them.
Not sure if there is a solution for this that we can do easily... we should probably store this somewhere on add-on upload.
Reporter | ||
Comment 5•15 years ago
|
||
(In reply to comment #4)
> I know nothing of multi-package add-ons... but my guess is we aren't storing
> them in AMO, and therefore I can't index them.
https://addons.mozilla.org/en-US/firefox/addon/7517/ is a multipackage add-on. I'm guessing you have the package ID in the database but not the ID of any of the add-ons within the package, which is exactly the reverse of the IDs that Firefox does version check and metadata checks for.
Assignee | ||
Comment 6•15 years ago
|
||
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Comment 7•14 years ago
|
||
Status: RESOLVED → VERIFIED
Updated•9 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•