I've been around for a really long time now.
Mon, Dec 11
We could move test2 to group1 and use that. Easiest solution, plus would get some extra traffic.
I already did those things in D902, needs a rebase.
Thu, Dec 7
In which case they shouldn't even have GlobalBlocking installed. But was also happening on plwikivoyage, so maybe not all fishbowl-related?
I wonder if this only affects fishbowl wikis, when someone tries to login with a CA account? Seems weird.
Wed, Dec 6
Mon, Dec 4
And for some insane reason I don't get, I'm no longer getting the weird import errors I had earlier--was able to update D902 just fine.
- Swapping coverage for pytest-cov (keep it in the dependency list though, sh.py uses it...weirdly)
Wasn't is_cached fixed in master?
Does this need to be an exception, or would logging it suffice? That would allow grouping on the user IDs.
Not quite, it's still a WIP there's a long tail.
Yep I think we're on the same page here.
Phab's already behind Varnish, Gerrit is not yet (cf some bug I don't have in front of me). But with objects this large can we actually expect Varnish to keep them in memory?
What will happen if we try to checkout a project with git-lfs-enabled submodules on tin?
Bah! Ok, reverting.
Both added to Phab
Broken? Or do they even exist? I can't find them in diffusion.
Fri, Dec 1
I don't think librarization of multiversion is the right way to go. If we want some sort of generic farming abilities, it should be in core or some library or an extension, not from repurposing multiversion (which, btw, I've slowly been trying to trim the edges of to make less complex).
Thu, Nov 30
I removed the error outright in 72960eedfb32b8a4c5dfccbd1651e08c7539d642
Was fixed in rMWe5b8bf
Function in question is SpecialPage:: run(), specifically the call to execute(). But really, this shouldn't happen. The only way I could see this happening would be if a caller to the SpecialPageBeforeExecute hook called unset() on the $subPage parameter. But even then, it's a scalar and isn't passed by reference...so how?
Raising priority because it's one of the most spammy exceptions as of today.
That's good for people on IRC. This task is more about making it clear from the browser when you open said sites. No matter how well downtime is announced, we're always going to have the person who didn't see the notification and starts asking on IRC.
Do we even gain much from having Phab speak http2 for an internal connection to Varnish?
Wed, Nov 29
They'll mirror just fine since Phabricator just observes upstream.
Adding author and committer from that change. Thoughts?
Tue, Nov 28
Yeah, good point. Should just be a straight revert?
Sun, Nov 26
Auto-signing from within Jenkins isn't a super huge priority.
Sat, Nov 25
Thu, Nov 23
Cuz I thought about moving this repo to Differential but never did. Could probably just drop them.