Actually, HTML mail has an issue now.

This is technically fixed now but the meme stuff is real old and rough so I'm going to maybe make some kind of effort to get through more of T5258, etc.

This is conceptually easy but no trigger character really makes a ton of sense. I'm going to decline this until it's more clear what the desired behavior actually is.

I've removed the requirement that prototypes be enabled and marked this as fixed in D19195. The behavior could probably be refined, but I think it should fail in an obvious way when it fails, now.

I believe the behavior of this UI should generally align well with what reasonable users might expect, now. In particular, /src/backend and /src/backend/ are now exactly the same in terms of actually resolving ownership, although the UI will continue to show you the value you entered (to avoid confusion where someone types /docs/README.md and the UI echoes back /docs/README.md/ and they have a reasonable concern that the path wasn't understood).

The easiest fix here is probably to just return an interstitial.

I've deployed these configuration changes to production and they appear to have resolved the issue.

Probably better is to add pathIndex

New, far wordier options available at HEAD:

Since I can't really figure out how to make this stuff segfault or what reasonable ranges for these values are, I'm tentatively going to lower these values to 10000 in production (based on sage advice from Rasmus in https://bugs.php.net/bug.php?id=36463) and see what that breaks.

On my system, this script:

Entering MFA credentials during an OAuth server redirect workflow can currently be blocked by the CSP.

PHI410 and PHI348 are both related to Differential's TYPE_UPDATE transaction. This is essentially the only Differential transaction which has not moved to ModularTransactions.

This log is now available at HEAD of master.

Just to briefly touch this:

This is effectively paused until I'm more convinced that the stabilizations changes really stabilized things -- I'm hoping to stabilize first, then work on improvements from there.

The corresponding support ticket was likely addressed by these changes. The remaining stuff here is still planned, but probably not moving forward any time soon.

The actual support issues were likely addressed or obsoleted by the above changes. The rest of this is still planned, probably won't move forward any time soon.

I had a lot of stuff come up this weekend, but made it through Kitava A5 with a Tectonic Slam Facebreakers Juggernaut (???) and an Arc Totem Hierophant, both around 51. Unsure how I currently feel about either character. I think I can turn the Juggernaut into Molten Strike if I find a decent weapon. Damage is okay so far on the Hierophant but my Haku is still at level 1 so fixing his resists has been tough.

I don't know how to reproduce this.

See T13098. I currently plan to expose the shell-complete workflow to every arc toolset, but I don't think being able to shell-complete bin/storage upgrade or similar is worth pursuing.

See T13098 for followup. Currently, I have ArcanistWorkflow generating a PhutilArgumentWorkflow but not actually subclassing it.

This has seen little interest so I don't currently plan to pursue it. Ideally, lint messages should simply include patches so that arc fixes the errors itself.