In T218485#5031203, @MusikAnimal wrote:

We could remove the hyphen and keep the parentheses, as you suggest, but I see nothing linguistically incorrect with the status-quo. I believe this presentation was the same in the older version XTools, so it's been around for years.

Hello, @Adithyak1997, thank you for the bug report. What exactly is the problem? Are you concerned about the fact that we put the word "Semi" in parenthesis? Are you talking about the word "HIde" which is in brackets? Or did I completely missunderstand?

A quick eyeball at the emails show it's a pretty standard "spoofing our email as a from address and reply-to address" spam. This happens about once every six months to a year but this is by far the biggest I've seen.

Since I did most of AdminStats, I’ll take this on.

And I've switched the instance to wm-bot, since that seems to be the standard in all of the tech channels.

I've set #wikimedia-tech and #wikimedia-dev to +rf #wikimedia-overflow. It's not an ideal solution but it is a solution, hopefully we'll be able to increase productivity in those channels. #wikimedia-overflow has a large op presence that can either invite users or solve the issues.

If you set a +r and +f, I would recommend #wikimedia-overflow, as it already has a topic with those instructions and a large chanop presence who can handle the messages as needed.

Actually, after further digging it appears to be related to Intuition. @Krinkle where would be the best place for us to request additions to language/mw-classes/Names.php?

It appears to be related to TranslateWiki, see message stats

Another option: Simply have wm-bot wait until it's identified before it joins channels.

From an initial look at things, looks like the database queries are timing out. This is probably related to the large number of revisions that AIV has.

I am assuming with the increased priority there is an increased urgency. As such, do we have a time-frame for when we want to upgrade to Symfony 4? I am ready to begin work on this as needed, we will need to coordinate roll-outs.

Saw the following in /opt/xmlrcs/nohup.out and restarted es2r.py. That seems to have fixed the feed, it immediately started reporting in #wm-bot again.

requests.exceptions.HTTPError: 502 Server Error: Bad Gateway for url: https://stream.wikimedia.org/v2/stream/recentchange
Traceback (most recent call last):
  File "./es2r.py", line 18, in <module>
    for event in EventSource(url):
  File "build/bdist.linux-x86_64/egg/sseclient.py", line 39, in __init__
  File "build/bdist.linux-x86_64/egg/sseclient.py", line 52, in _connect
  File "/usr/lib/python2.7/dist-packages/requests/models.py", line 893, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 502 Server Error: Bad Gateway for url: https://stream.wikimedia.org/v2/stream/recentchange
Terminated

OK, fair. I read that comment the exact opposite way. I'll do some more digging on my end, per discussion on https://github.com/x-tools/xtools/pull/202, it appears to show up in only adminscore, but I will continue to dig here and make sure XTools doesn't wind up confused in the future.

@Marostegui Is that an acknowledgement that the problem is fixed or that you won't be looking at this obvious issue?

See https://github.com/x-tools/xtools/pull/202

Ok, so looking at the results we're pulling, for enwiki we're getting the following:

"source" => "edit-count"
"value" => "9666"

Appears to be a intuition error parsing a language file. I shall dig.

https://phabricator.wikimedia.org/p/238482n375/ - Sweeping changes to a collection of tasks. Biggest impact was setting bugs to secure only and removing subscribers, essentially hiding bugs from projects.

Unfortunately, XTools doesn't have access to anything Flow. See T136950 for details.

Closing this task now, as I haven't seen this recently. Will re-open if there are issues.

Makes sense.

In T193838#4183255, @JJMC89 wrote:

In T193838#4183239, @Matthewrbowker wrote:

not display the automatic removal when manual removal happens?

That would be my suggestion.

This makes a lot of sense. I'm not opposed, but we'd have to make some serious changes to the database engine on the XTools end to make it work.

That's a fair request, we'll see what we can do.

Honestly, I don't know what to do with this task. When I first looked, I remembered seeing the titles mentioned, but since I don't know German I don't exactly know what's being asked.

@A2093064 What are you recommending with this task? To not display the automatic removal when manual removal happens?

There has been no information from the Apple side of things either, the bug report I submitted on February 17 is still open. Will re-open if there's something actionable on the WMF end, but since plain text isn't affected I'm almost positive it's a Mail.app bug.