Piledriver would also benefit from having some functional equivalent of destroying an Almanac resource. This can be implemented as a piledriver.destroyed property, but a formal disabled state would be cleaner. PHI1331 is vaguely related.

• When Piledriver destroys a resource pile, it's helpful if it can read the entire authoritative state from sources by using only a pile ID.
  • EC2 can do this with "DescribeTags".
  • Almanac currently can not. Almanac types should support searching by property value.
    • This could be directly on almanac.*.search.
    • Or this could be generic, via T12799.

Problem 2: Arcanist does not check that messages emitted by linters have a valid line number.

Problem 3: The cpplint unit tests fail, and the failure appears to be pre-existing and significant.

• Problem 4: If a file ends in non-newline whitespace, the text linter may raise a message which removes that line. The renderer then tries to highlight part of it, which fatals.

Here's a simplified reproduction case for "Problem 1":

• Problem 1: cpplint may raise messages at line 0, but arcanist can not render these messages after the severity of runtime-level errors was increased in D21044.

Effectively mooted by T13542.

I've written some Terraform-class tooling which can likely automate all the actual hardware allocations. This needs some more work, but I believe the tricky stuff (mostly: representing resources and allowing templating to reference resources which haven't been built yet) is at least working.

Subnet/NAT issues in T12816.

Continued in T13542.

The major offender here (services per instance) was fixed by updating caching, and I destroyed all the old services. This is perhaps spiritually continued in T13542.

Continued in T13542.

Continued in T13542. I wrote a Terraform/CloudFormation-style service in PHP over the last couple of days.

Continued in T13542.

Committer identities ... they're currently stored in a JSON blob so there's no efficient way to query them.

Is there a way to find which object(s) an (unmapped) identity was discovered on?

• In previews, suggestions aren't highlighted properly (likely just missing CSS).

Since many of these options probably don't have "right answers", I'm trying this reasonable-seeming variation on some repositories which seem like they'll benefit from a repack:

• Ignore selected elements that are not part of the current changeset.

• n, etc., can incorrectly select blocks inside a diff inside a suggestion.

See PHI1748. I ran a query against a subset of instances to determine how widespread usage of "Dark Mode" is, to help inform a decision to either implement the mode properly (see T12311) or remove the mode. The query was of this form:

I think (?) this was pretty much resolved by the last round of changes. See T13291 for some followups.