Assessment for prioritization:

Support: Medium
Feasibility: Medium+ (looks like it just needs to fragment the cache on user language)
Impact: Low
Risk: Low

Priority: Low

@Qgil, this is the ticket I mentioned to you earlier today. We aren't going to take this -- it might be appropriate for dev relations?

Just for context: why is this task in your radar?

@Aklapper, any ideas of how to help fixing it? I was thinking that perhaps it could help to send an email to the Labs mailing list asking for volunteers to fix it, or at least to assess whether this is a good task for Google-Code-In-2015 (and mentor it).

This task was initially filed under Community-Tech so if Community-Tech is not going to take it I propose declining it here in Phabricator.
https://github.com/x-Tools/xtools/issues/60 is the canonical bug report. Krenair commented how to probably fix the issue. Hence it's the usual situation: Someone needs to come up with a patch and I don't know how active the tool maintainers are (and hence if they could mentor anything)...

OK, thank you for the extra background. CCing some contributors to that GitHub repo, hoping that at least one of them is interested in volunteering as Google Code-in mentor? This task does look like a good candidate for it.

This is also a pitch for developers of tools in Labs to consider Google Code-in 2015 as a program to get a bunch of bugs fixed by students. :)

In T111512#1781470, @Aklapper wrote:

https://github.com/x-Tools/xtools/issues/60 is the canonical bug report. Krenair commented how to probably fix the issue.

You mean Krinkle?

Either way, since this tool's issues are apparently tracked in Github, should probably be marked invalid.

Ahem. Yeah, sorry. I'll stick to writing Kr*n*** from now on. :)