Thu, Sep 19
Current sequential install time with npm install takes:
npm install 144.30s user 63.94s system 75% cpu 4:35.22 total
Wed, Sep 18
Tue, Sep 17
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
Mon, Sep 16
Fri, Sep 13
Thu, Sep 12
Wed, Sep 11
Tue, Sep 10
Mon, Sep 9
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.
Thu, Sep 5
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.
Wed, Sep 4
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
Tue, Sep 3
Mon, Sep 2
Fri, Aug 30
Moved to stalled since not touched for more than two weeks.
Thu, Aug 29
Wed, Aug 28
Tue, Aug 27
Tests that are not run by CI
Mon, Aug 26
I think I favour option 1 assuming that the service we are planning to implement is the Prometheus based one.
Aug 24 2019
Looks to me like this is no longer UBN.
Aug 22 2019
Backport is now merged and testing on both test.wikidata.org and wikidata.org seems to show this no longer happens.
Aug 21 2019
Looks like this bug always existed in our code but it became apparent with the flipping on of termbox on Wikidata.