Exception: Unknown key in Tree Status response: tags in mozautomation/treestatus.py
Categories
(Developer Services :: Mercurial: mozext, defect, P3)
Tracking
(Not tracked)
People
(Reporter: sfink, Assigned: sfink)
Details
Attachments
(1 file, 2 obsolete files)
Recently, the treestatus response format changed, and mozautomation's treestatus.py throws an Exception on any unrecognized key.
| Assignee | ||
Comment 1•7 years ago
|
||
| Assignee | ||
Comment 2•7 years ago
|
||
| Assignee | ||
Updated•7 years ago
|
Comment 3•7 years ago
|
||
Steve, can you send this on Phabricator, and tag me for review? Thanks.
Comment 4•7 years ago
|
||
| Assignee | ||
Comment 5•7 years ago
|
||
| Assignee | ||
Comment 6•7 years ago
|
||
(In reply to Rok Garbas [:garbas] from comment #4)
I'm not aware of a reason why checking full api response is actually needed.
I would ignore fields that you are not using in the script. That would make
it more future proof if there will be another field that will be added, for
whatever reason.
Sorry, I shouldn't have tagged you for review (but I was leaving and in a rush). Connor is a better one to make decisions about what makes sense for this code. I also don't have a reason to go one way or the other, I was just mostly following existing style. I've redirected the review to Connor.
| Assignee | ||
Updated•7 years ago
|
Pushed by cosheehan@mozilla.com:
https://hg.mozilla.org/hgcustom/version-control-tools/rev/fdb9aada493e
Handle new keys in tree status response, r=sheehan
Description
•