Page MenuHomePhabricator

Debug EventLogging ExternalLinksChange
Closed, ResolvedPublic

Description

Try to do a bit of debugging as to why the EventLogging ExternalLinksChange doesn't work as expected.

To speed up debugging we need to be able to rapidly push changes to a local copy of the spam blacklist extension (logging to file etc.) and do controlled testing on a MediaWiki install. Obviously we can't do this with the production extension and we don't want to continue testing on the production test.wikipedia.

Therefore, we could try:

Once testing, throw findings up on this wikitech page and discuss with T115119

Event Timeline

Investigating the possible options:

Local MediaWiki-Vagrant

  • Pros
    • Quick
    • Easy
    • Doesn't need operations/task creation/instance provisioning
  • Cons
    • Not easily public
    • Cannot be tested by team
    • Not entirely sure how EventLogging works on a vagrant install

Beta cluster

  • Pros
    • Well written guide
    • Public
    • Easily accessible for testing
    • Supported by the awesome ops team
    • Apparently designed for this sorta stuff?
  • Cons
    • Never used it
    • Need to be assigned root
    • Likely many phab tasks and discussions needed

Labs project instance

  • Pros
    • Really great guide exists
    • Public
    • Easily accessible for testing
    • Entirely "ours" so we can throw some nasty debugging code together and not worry all too much (well now they'll never let us have it!)
  • Cons
    • Looks a little involved
    • Less support from the awesome ops team
    • Never used a project instance
    • Responsible for a VM

@Samwalton9 any thoughts? The beta cluster is apparently designed for this kinda stuff but we'd need to be a little more considerate - if we did have our own instance it would (hopefully!) be short lived and wouldn't take up too many resources and we could focus less on being considerate and more on getting to the root of the problem.

Once we'd identified where the bug is we'd need to prod a MW developer who knows how to tick all the boxes (code standards etc etc) to package it all up and push it upstream

Thanks for looking into this! Looks like Beta would be the best bet. I guess we need to get the schema deployed there?

Looking closer at the beta cluster (this section in particular) it appears it may not be suitable for development. I think we should still enable the schema there and use the above "how to verify events" section for some further testing. I'll see if there's somewhere we can use as a "development playground"

I've learnt the following:

  • Beta cluster is designed for staging/testing - we should enable the schema there

Reference P4938

With T158210 completed we now have access to a project for testing - I'm in the process of setting up an instance of MediaWiki-Vagrant for this

Instance set up - just trying to get the EventLogging in general set up so we can start debugging