I've barely had a chance to play recently but I know everyone is longing for an update so: I made it to level 88 (which I think is the highest level I've reached on any character), and completed all the white maps, and haven't died yet.

Much of this survives in T13110 but the rest is resolved.

See Planning.

After clicking 17,000 emails I successfully transferred everything to AWS, with some minor caveats:

I moved SSL and registration for phurl.io to AWS in T13113 so this is just a transfer issue now.

oh wow it actually worked 😱

AWS also supports DNS-based authorization now, which reduces the need for all the MX juggling.

I was able to MX phurl.io and get an SSL authorization link working. I moved phurl.io SSL to AWS ACM so this (certificate expiration) shouldn't happen again.

(See also T7125, but this particular problem has conceptually been solved for every domain except phurl.io by using AWS certificates.)

See also T12917 and a brief mention in T13062.

Actually, it seems like rel="noreferrer" fixes this. This is bizarre so maybe this is a problem with a spooky ghost haunting my computer?

That's a reasonable point. The details of PHI386 weren't very indicative one way or another since I didn't end up GC'ing the repository multiple times. I suppose I can go GC it again during the deployment window this week and see how long it takes.

Modify the PushEvent table to contain more information about locks and waits (e.g., active queue status; how long the push waited for the write lock; how long the push spent synchronizing).

I kind of wish I could see PHI415. Do people send in support tickets about path of exile?

wow every piece of gear you have is better than all the gear I own put together

See PHI431. See PHI426. ... I suspect these lead to T731 and T10574, practically.

See PHI483. There's currently a bad interaction between builds completing and drafts unpublishing, described in greater detail in T13108.

On complex build statuses, which has come up more than a handful of times but which I haven't aggregated well:

(Note that it will only work for more-recent logs, T13088 will have some guidance for older logs eventually.)

I missed this task when collecting T13088, but this is supported after D19151.

This is sort of a race. Here's what happens:

I only play True Ethical SSF Hardcore so I have of never seen a Kaom's or worn a piece of gear with more than 4 links on it, and I'm definitely not very good at the game, but one thing that's been going better for me this league is that I've been doing builds with critical strike.

D19240 exhibited the same behavior on a local lint failure so this is almost certainly a mundane bug rather than some sort of exotic race.

I had a local test failure there

From reading the code, the behavior should already be (A): that is, we should already get this right in cases (3) and (4).

See PHI483. Some of the mail rules around builds and drafts are kind of whack right now.

I removed this in rCORE36d2ef5dffe441ba1175e362bb73f0e43a9f70a2.

See also T13102/PHI442. The MySQL setting optimizer_search_depth=0 may fix the weird explosive complexity here.

The Arc Hierophant is still alive, but he managed to get a Scaeva to drop shortly after the last update. I brought a Reave Juggernaut to 82 with it, although I've only made 1-2 tiers of progress in maps.

Ideally, I think Diffusion, Files and Paste should all have the highlighting/encoding options and share more of the same code, with Diffusion being distinguished by having blame (and, I suppose, symbol linking) available.

The task.open-count.status counts open tasks that are the result of a status change (an existing task being closed, or a closed task being reopened). Since it's much more common for existing open tasks to be closed than for existing closed tasks to be reopened, the series should go negative pretty quickly and stay there over time, more or less ending up with a big negative number of "number of tasks ever closed".

What steps did you take to try to find the documentation?

See PHI364. An install encountered a held lock issue...

See PHI364. An install encountered a held lock issue in a cluster which resolved itself immediately when I appeared onsite.