Resolved after creating new secrets
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Yesterday
Fri, Sep 11
Thu, Sep 10
Wed, Sep 9
Tue, Sep 8
Sun, Sep 6
Sat, Sep 5
Thu, Sep 3
Wed, Sep 2
If maxlag is an imperfect indicator of overall server load anyway, I think it would be reasonable to consider exempting certain read operations from throttling, or perhaps read operations in general could be given a higher maxlag threshold, especially where we know that they impose very little load. Also, I think some kind of priority aging would be more appropriate for bots, rather than keeping them waiting for days.
Tue, Sep 1
In T421642#12271821, @JeanFred wrote:As I wrote back in T244030 (which was T242081: Pywikibot fails to access Wikidata due to high maxlag lately back then):
In T244030#5842377, @JeanFred wrote:
Mon, Aug 31
@YuviCodes: Split your patches into smaller parts with 5-10 files. Also run pre-commit before committing.
Sun, Aug 30
Sat, Aug 29
Fri, Aug 28
@Epidosis: The impact is not solely for Wikidata.
In T399485#12263795, @bd808 wrote:With T426484: Add proxy support to GitHub actions implemented is the general problem solved for your needs now @Xqt?
Tue, Aug 25
In T435959#12252172, @RhinosF1 wrote:I'm very confused, the logs are full of undefined array keys but this started just a few hours ago. The code hasn't changed in months.
Two other clusters are also down:
Mon, Aug 24
See also T435699.
Sun, Aug 23
There are also other tests failing: all tests of TestIndexPageMappings and all tests of TestIndexPageMappingsRedlinks except test_index_redlink.
In T435715#12244246, @Mahveotm wrote:it can be added as a sub-task to this T434934, or what do you think?
Pywikibot on Toolforge is five releases behind the current upstream stable version, 11.7.0. Is there an issue preventing regular updates?
Sat, Aug 22
Thu, Aug 20
The new matrix might be here: https://meta.wikimedia.beta.wmcloud.org/wiki/Special:SiteMatrix