This warning indicates that database table (oathauth_users) is not updated

I ran update.php. @MarcoAurelio can you login now?

but.. have those db changes run on WMF production already then, because otherwise this might turn into a production issue. I only see a note of them having been deployed to beta.wmflabs

In T228250#5340777, @Nikerabbit wrote:

I ran update.php. @MarcoAurelio can you login now?

Yes, I could successfully login now. Thanks @Nikerabbit.

In T228250#5340798, @TheDJ wrote:

but.. have those db changes run on WMF production already then ? I only see a note of them having been deployed to beta.wmflabs

I think this is an important question.

In T228250#5340804, @MarcoAurelio wrote:

In T228250#5340798, @TheDJ wrote:

but.. have those db changes run on WMF production already then ? I only see a note of them having been deployed to beta.wmflabs

I think this is an important question.

Given the patch metadata says Branches master, wmf/1.34.0-wmf.11, wmf/1.34.0-wmf.13, wmf/1.34.0-wmf.14 I would say it's likely that the changes have been done in WMF production, because otherwise we would have noticed already.

Seems WMF production database had some schema changes recently for the oauth_users database table:

• T225643: Schema change to oathauth_users
• T226826: Drop old oathauth_users columns

We do not seem to have any such error on WMF production. I thus guess translatewiki.net lacks the database change from MediaWiki-extensions-OATHAuth potentially because it is missing a database patcher for update.php?

In T228250#5340833, @hashar wrote:

Seems WMF production database had some schema changes recently for the oauth_users database table:

• T225643: Schema change to oathauth_users
• T226826: Drop old oathauth_users columns

We do not seem to have any such error on WMF production. I thus guess translatewiki.net lacks the database change from MediaWiki-extensions-OATHAuth potentially because it is missing a database patcher for update.php?

No. It’s just because update.php wasn’t run. As evident by Niklas running it, and Marco being able to login

Prod was done, there are two tasks for it

Thanks for the help. For the record, I have added OATHAuth to the list of extensions I receive notifications for merged patches. But I wonder if there is a better way to make people aware of mandatory schema changes?

One of the reasons I'm not running update.php every time is T160993: MysqlUpdater::doWatchlistUpdate is very slow

Hurrah :]