Current sequential install time with npm install takes:
npm install 144.30s user 63.94s system 75% cpu 4:35.22 total

Still picking this up to do since there is no point in delaying. Ticket for using this can be found at: T233097

This is blocked by two things:

• Having a CSR to put the component on
• Being able to localise the component

We're postponing this task a little bit until we know more what our vue/JS interface will be like

In T232193#5474967, @Lucas_Werkmeister_WMDE wrote:

If you need more data in the hook, you can just add extra arguments to it without making an incompatible change (or am I misunderstanding something?).

This means keeping this part of statement saving basically the same. We'll still be using this old-ish (but obviously working) code for saving changes to statements.

We are imagining perhaps altering StatementChanger.js with something like

Moving back to needs work since that's what we seemed to say in the last story time.

I tried the same from codfw's deployment host and saw the same. No obvious difference between api-ro and mwdebug1001 in the time to respond.

I think this is probably the same as T229313. We suspected it might be related to T231011; perhaps the new train makes this problem more pronounced

Looks like this is because the tests create a real OutputPage object who's language is derived from the RequestContext.

We went another way and used simulated traffic

Moved to stalled since not touched for more than two weeks.

Tests that are not run by CI

I think I favour option 1 assuming that the service we are planning to implement is the Prometheus based one.

Looks to me like this is no longer UBN.

@Lea_Lacroix_WMDE @WMDE-leszek We have, after some delay (sorry), merged the revert patch.

Backport is now merged and testing on both test.wikidata.org and wikidata.org seems to show this no longer happens.

Looks like this bug always existed in our code but it became apparent with the flipping on of termbox on Wikidata.