I think (?) this reproduces for me, too:

See PHI11. This has material impact when using PhabricatorRepositoryRefCursorQuery to query landing targets, and likely impacts the logic in DifferentialRevisionOperationController.

I'll look at the pricing breakdown and I might do some perf testing just to see if there's any real difference.

22280->22280 for aphlict (or we could possibly use path-based routing on the ALB instead of opening up a 2nd port?)

Cool, that all sounds like it's roughly what I expected. Thanks!

Let's just take another look at this during/after T10448? I think that's happening soon enough and this is minor enough that it's probably not worth fixing separately.

Inbound mail seems to be working now.

This is very minor, but blue-underneathie is still active even though repo012 is dead, which is causing the queue to spawn impossible backup jobs that sit there retrying forever. They should fix themselves once the instance is suspended. I'll likely pursue the remaining cleanup here shortly since we haven't seen any issues in a few weeks.

Inbound mail later bounced. I think the issue is that we have a *.phacility.com MX record, but an admin.phacility.com A record. I can't recite all the wildcard vs nonwildcard DNS rules offhand, but I think the A record is shadowing the MX record, e.g. dig mx admin.phacility.com does not produce the right results. I've added an admin.phacilty.com MX record which might sort things out once it propagates.

The new paid support application is now in closed beta. This will become publicly available in the relatively near future, then become then channel for SAAS support after that. It may later become the channel for some types of free/community support (most likely bug reports, per above) but this probably won't happen for a while.

Community and us can both use the normal task form to report bugs -- the "bug report" form just had extra instructions.

That is, the flow would be one of these:

Let's just do Discourse for now? I don't plan to get anything up on admin for at least a while.

Using @mentions in issue comments hits a policy exception because of the slightly odd way pact policy filtering works.

This works now: PHI1

Test mail from the console now gets routed/accepted properly but real mail still doesn't. I'm going to write this off as possibly being a route propagation issue for a little bit and see if it fixes itself.

Email replies don't actually work since mail gets routed to the web tier (mail.phacililty.com) which can't hit admin. I think I can fix this with a mail route.

Some stuff I'm thinking of doing in the short term:

This is entering some kind of closed beta shortly, I'll follow up in T12904 for actual feature improvements to the Support application.

Ah, that makes sense. Everything else sounds entirely reasonable to me on the "VPC per customer" plan.

bastion host per subnet

I think we end up more consistent overall if "Resign" and "Accept" have the same behavior in this case.

From reading the code, resigning (instead of accepting) probably also leaves the revision in "Needs Revision".

It looks like the price difference is pretty large -- $45/month for a m4.large reserved instance vs $80/month for a m4.large dedicated -- plus ~$1,500/month/region for having at least one dedicated instance. It would be easy to start using dedicated hosts in the future, right? Just an issue of converting existing hosts if we run into issues?

Another correction, Puppet doesn't //need/ a dedicated server. You can run Puppet in a standalone (agent) mode, if you are willing to somehow get your Puppet manifests onto each host that you wish to provision.

In T12856#227621, @amckinley wrote:

Terraform Review
Pros:

• Written in Python, which everyone knows is superior to Ruby in every way

A customer is hitting an issue where pushes to staging areas do not push LFS objects. I'd guess this is an LFS upstream problem based on a hazy recollection of events here.

FWIW, I am actively working on a Puppet module for Phabricator, see https://forge.puppet.com/joshuaspence/phabricator.

AWS doesn't have a single device which can both listen for TCP on 22 (only ELB) and terminate SSL for websockets (only ALB).

I don't see an "Email Settings" panel, am I missing it or did you mean a different panel?

T4411 discusses some similar issues, although it predates Spaces and focuses on subscribers rather than assignees.

Ah sorry, I should've made that clear. Yes, I am able to reproduce the issue on our installation.

In T12907#228951, @chad wrote:

This is not a test install.

That is, I think the right tool for the job is either runtime enforcement or lint enforcement: make unittest.skip() with no reason fail (so the tests don't pass) or make lint raise a warning like "unittest.skip() must have a comment above it explaining the plan for re-enabling the test.".

Can you change the syntax to something like @unittest.skip("Reasoning behind this decision...")?