In T310759#8038990, @Amire80 wrote:

In T310759#8024944, @Diesel_kapasule wrote:

@Amire80 thank you for the explanation.

You're welcome. Can anyone merge https://gerrit.wikimedia.org/r/c/mediawiki/extensions/IPInfo/+/808128 ? :)

Thanks @Prtksxna - filed as:

• T311724: Display generic error message on Special:SimilarEditors
• T311536: Display some errors returned from Similarusers on Special:SimilarEditors
• T311535: Display error on Special:SimilarEditors when the database is being refreshed

@dom_walden This should be ready to test locally now

In T310646#8028643, @dom_walden wrote:

In T310646#8026239, @Tchanders wrote:

@dom_walden If beta is now broken, I may need to revert the patch for this until we've fixed the production config - let me know if you find this is the case before I do...

Beta appears to be working fine. But then again it is using the mock client.

If testing locally, you'll need to update flask_config. Now I think about this, the config on production presumably need updating too. @hnowlan do you know how we can do this?

Thanks @dom_walden - the new patch should fix it.

Could this be solved by adding <bdi> tags around the title?

In T311030#8020367, @AGueyte wrote:

We have a slight design issue here, the help popup is melting with the sidebar text, should I fix it in this patch or create a new ticket?
cc @Tchanders

{F35264850}

In T308670#8009598, @Niharika wrote:

@Tchanders is there a list of users who will have access to the service if we host it on beta?
On slack I heard you say that "global steward rights group" will have access. Who is on this group? This task description states -

The SimilarEditors extension provides an interface via MediaWiki to the Similarusers service. It is available only to users who have the similarusers right.

Who all have this right?

Basically if we can ensure that the service will only be available to a limited, trusted group of users then we can host it on beta. Otherwise not.

Thanks for this @Isaac - we'll take a look.

@Prtksxna 'Connection type' is currently not displayed if it is the same as 'Connection owner', and instead is shown as 'Not available'. Since this now means the data is missing, I've changed this in the patch I've uploaded, so that it now displays even if it's the same. Is this ok? If not, what should we do?

Ah, I thought because we were iterating over user_edit_indices that we had already filtered out items without the "user" key; however, we're also adjusting the indices from the original array (related code). The new patch should fix that.

As discussed in a follow-up meeting, @Niharika agreed to removing the ipinfo-enable preference for now. Filed as T310819: Remove 'enable-ipinfo' preference while IPInfo is a BetaFeature.

I think we can consider the documentation improved, and move this task on. Let's keep maintaining the documentation, of course.

Now that PrivateSettings.php is updated, I believe all we need to do is configure the URL for the service. @Niharika Can we use the real service on Beta?

In T308649#8008031, @Prtksxna wrote:

Thanks @Tchanders. Wanted to confirm that the time out error (last one in the table) isn't recoverable and trying again later won't help.

Working on the messages now and will share them soon.