I can co-lead here as well.
Fri, Oct 18
Wed, Oct 16
Tue, Oct 15
I'd say I usually get a week or so, but it feels like it's happened every other day or so lately. Latest release channel Firefox / Debian, mostly on a single machine.
Sun, Oct 13
@Quiddity thoughts here?
Sat, Oct 12
@josephine_l I'm primarily attending as a note taker, and should probably focus the time I'm not doing that on local dev and CI sessions. At any rate, I suspect there are considerably better-informed folks than me to lead this one...
Fri, Oct 11
One suggestion for a focus: Maintenance & cleanup of existing docs. This has come to mind thinking about docs and new developer onboarding - there's a ton of material but it's not always clear how it relates to the current state of things or how to navigate it. Technical debt lives in the documentation as much as anywhere...
Jeena's comment above covers it pretty well. We have a local k8s proof-of-concept with Minikube that I think could be used for basic MediaWiki development right now, but the work has led to questions about complexity both for users of the development environment and for maintainers of the environment itself.
It's likely worth mentioning explicitly that we've landed on Argo, after building out and evaluating proofs-of-concept for our final three candidates (Argo, Zuul v3, GitLab CI).
Thu, Oct 10
Wed, Oct 9
Fri, Oct 4
Wed, Oct 2
14:05:54 brennen@inertia:~/code/wmf/mediawiki/core (540214-publish-to-dev-1 m0/u0) ☙ docker pull docker-registry.wikimedia.org/wikimedia/mediawiki-core:dev dev: Pulling from wikimedia/mediawiki-core 5c86276767f3: Already exists 0445fd56950a: Pull complete 4edf12b6f5f0: Pull complete 39961bb3a06a: Pull complete ff1bd3a20a43: Pull complete c8d5cc47c664: Pull complete f94c56cc4983: Pull complete 85fda2ab69ff: Pull complete 83f2db0c0f14: Pull complete 3e206fad26b2: Pull complete 739d2f3bb1ec: Pull complete 4c24a7cd82b0: Pull complete 006500bbde5a: Pull complete 332ecb8ca00f: Pull complete 045acbcfc608: Pull complete 061f4db22d8d: Pull complete 7df152ecb998: Pull complete aaee8cf224ae: Pull complete 64dd4ce38455: Pull complete 7ee82f4825b9: Pull complete 3cd5842b704b: Pull complete 27ca13914671: Pull complete 39017c08604a: Pull complete Digest: sha256:5463c6232eee78a6300c40daea12b72e71362d9289e2e05f5d4f1097abec0b01 Status: Downloaded newer image for docker-registry.wikimedia.org/wikimedia/mediawiki-core:dev docker-registry.wikimedia.org/wikimedia/mediawiki-core:dev
Tue, Oct 1
Mon, Sep 30
Shall we declare this Resolved?
Sep 9 2019
Aug 22 2019
Aug 9 2019
Seeing 3659 of these (or pretty similar) since 03:30 UTC:
Aug 8 2019
Aug 7 2019
I'm assuming related:
Aug 6 2019
Several of what I believe is the same issue logged in the last hour:
Aug 1 2019
Thanks all. I'll roll this forward shortly.
I am making the assumption at this point that this one is safe to remove from train blockers, given likely volume of errors / impending hack. Please correct if I'm mistaken.
Jul 31 2019
It's a non-trivial amount of logspam - some ~1000 log messages a minute when deployed to Group1 - and will make diagnosing other issues correspondingly more difficult if rolled out.
A fuller message in case the ErrorException is relevant:
Changing priority to UBN!, as this is listed as a train blocker.
Jul 30 2019
Thanks for investigating!
Not rolling back Group0 for now.
Looking through changelog, Aaron seems to have commit messages with cache-related stuff. Adding for that reason.
Setting UBN! and adding as a train blocker. Not rolling back Group0 for now.
Jul 29 2019
Moving to UBN!, as this is a train blocker.
Does this just need us to update Heterogenous deployment/Train deploys?
Jul 19 2019
Yep - my last comment here turns out to be wrong and I think this will work, getting a version of https://gerrit.wikimedia.org/r/c/mediawiki/core/+/508392 into shape.