D19266 adds some additional Support Pact adventure mode content. Some other ideas for improving this mode:

See PHI496. Multiple users have now reached the maximum level ("Heavy Wizard") on their Support characters, and we're overdue for an expansion pack to add new adventure content.

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

Changeset rPfb4ce851c4ae: Add a PDF document "rendering" engine allows to view PDFs from the Files application. However, {Fxxx, ...} references to a PDF file in Phriction still only allow to download the file or open a lightbox with only an icon (again with a download link).

I really like this, Remarkup idea, I think there are many text based files that people add to reviews which would be easily transformed to something more readable by being transfer directly to Remarkup, even for example something as simple as CSV,

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:

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

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.

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.

I'm wondering how this should interact with T8407: Control diffusion's syntax highlighting.

It would be great if there was an ability for installations to write custom viewers for formats that are either more obscure (MIF Framemaker format), or even in house formats (.myformat)

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".

Not sure if it's expected in the current state, but here's one that doesn't seem well-formed: https://secure.phabricator.com/fact/chart/?y1=tasks.open-count.status

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.

It appears that MYSQLI_ASYNC depends mostly on mysqlnd ("MySQL Native Driver"). This has been the default since PHP 5.3 was released in 200 BC, but Ubuntu, at least, unbundles it and you can still install php5-mysql (non-native driver). Compounding this, we currently recommend installs install php5-mysql (bad), rather than php5-msyqlnd (good).

While testing D19215 I ran into this behavior in Asana:

When phage is executed against a large number of hosts, a bunch of the processes fail immediately. This is likely easy to fix, either some sort of macOS ulimit or one of the sshd knobs. This isn't the limiting factor in any operational activity today but will be some day.

That's probably it for promoting this week, see T13102 for next week.