Closed qdzlug closed 4 years ago
yah.. I've seen that before. IIRC it was because Jira's API returns invalid XML if there is a non-ascii char in a ticket title or some other field... in some cases. I remember trying to get jirash to be more defensive here but failed initially. Good to keep this here for now. I need to get jirash to spit out relevant context.
Commonly see it as the terminal escape character, which in the verbose xmlrpc dump (change verbose=False
to verbose=True
in jirashell.py) is 
.
^^^ that change allows one to more easily see the xmlrpc output that is causing the parse failure at least.
jirash v2 (first released 2017-11-10) was re-written in node.js. This issue is for jirash v1, which is no longer supported so I'm closing this as "won't fix".
Hi Trent,
Hitting this failure when trying to list out issues - the full run with both the numeric filter ID and the actual filter name are below.
Jay