Mon, Oct 19
Thu, Oct 15
Tue, Oct 13
Fri, Oct 2
Didn't find anything in the docs or poking through configuration. Might be worth asking upstream.
Thu, Oct 1
Wed, Sep 30
Tue, Sep 29
GitLab, if we end up migrating there from Gerrit
@thcipriani did some poking at this the other morning.
Mon, Sep 28
Work in progress: https://www.mediawiki.org/wiki/GitLab_consultation/Workflows
Thu, Sep 24
Wed, Sep 23
Tue, Sep 22
Sep 21 2020
see above for wtf php lol
Sep 18 2020
Sep 17 2020
Seeing a few of these in 1.36.0-wmf.9:
In wmf.9, seeing a handful of:
Continuing to see these in 1.36.0-wmf.9.
This seems to be fixed, so tentatively resolving. Not sure if we should backport this.
Sep 16 2020
End-of-day here, passing back to Lars.
Fixed from wmf.9 train perspective.
Per discussion in log triage meeting, doesn't warrant a rollback but should be fixed before we roll forward to all wikis.
Seems reproducible at these URLs, at least with a mobile client. (I'm fuzzy on how MobileFrontend actually works.) I don't see obvious user-facing breakage, but I may not know what to look for.
This looks to me like a probable train blocker; ~35 or so since rollout of wmf.9 and still happening at a low level.
Sep 15 2020
those ones relate to https://gerrit.wikimedia.org/r/c/mediawiki/skins/Nostalgia/+/623959/2 (T258001) and have already been fixed
I'm currently seeing a pretty steady stream of these in production logs:
Sep 14 2020
L&L given earlier today.
Sep 11 2020
While the gitlab box is now accessible via a floating IP at gitlab-test.wmcloud.org, there's a separate issue here with how SSH is configured on cloud VPS instances - it attempts to auth against LDAP but doesn't fall back to local users like the git created by the GitLab omnibus Chef config. There might be a workaround for that, or maybe we can add a separate sshd.
Sep 10 2020
or b) stop using the shared HTTPS proxy and handle TLS termination yourself
Thanks! I think I also need to ask for a hostname - that is, ideally people should be able to SSH to gitlab-test.wmcloud.org, and I don't think I can point that at the floating IP myself from Horizon? (It also conflicts with the existing web proxy.)
Yeah, see T261900 - I need to re-open that for a hostname, I think. In the meanwhile I'll configure it to give out the IP address, since that should remain static.