Open
Bug 1113593
Opened 10 years ago
Updated 10 years ago
bzexport fails with "Unknown Bugzilla error" when people change bugmail address because of its cache
Categories
(Developer Services :: Mercurial: bzexport, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: Gijs, Unassigned, Mentored)
Details
(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/4241] [lang=py])
This is annoying and I always forget and the error message is unhelpful:
Error: Unknown Bugzilla error. Title: 'Match Failed'
abort: HTTP Error 400: Bad Request
The ideal solution would be that bzexport should re-try the request and send the literal reviewer string I just tried to use.
If that's too hard to implement, at least it should give me a better error message, so it doesn't take me a full day to work out that Mossop changed his bugmail address and thereby broke all my review requests...
Comment 1•10 years ago
|
||
The code is at http://hg.mozilla.org/hgcustom/version-control-tools/file/e5016985d110/hgext/bzexport/__init__.py . In particular, the find_reviewers method is where the cache short-circuit occurs. If we were to implement the retry behaviour, we would need to extract the call to create_attachment into a separate function and update the reviewers and feedback keys of extra_args with new lists.
Mentor: josh
Whiteboard: [lang=py]
Comment 2•10 years ago
|
||
The other possibility is to diagnose the failure by catching 'Match Failed' errors and then checking any reviewers/feedback emails listed one by one by comparing the result of the load in find_reviewers against the cached value.
Updated•10 years ago
|
Whiteboard: [lang=py] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/4241] [lang=py]
I just hit this trying to request review from :mats (who recently changed bugmail from his gmail to his mozilla.com address).
I worked around it by removing the line:
:mats = matspal@gmail.com
from ~/.bzexport .
You need to log in
before you can comment on or make changes to this bug.
Description
•