See PHI54 for some additional discussion.

Unclear if building a search engine by just doing a lot of JOINs actually scales or not. Seems OK here.

See also PHI45.

See also PHI52.

No, we don't want to bring anything upstream if we don't support or maintain it.

See also PHI48.

A prototype of this is now available on this server (secure.phabricator.com). You can access it in Maniphest by using the Query (Prototype) field instead of the Contains Words field.

I think there will be a trickle of these for a while, but we seem to have found the most common cases.

We'll consider offering instances in the Sydney region in the future, but this isn't really a valid feature request or bug report. Feel free to continue discussion on Discourse.

This is now in the wild, and nothing seems to have cropped up yet.

The behavior may have changed, but the change is from "we sometimes silently do the wrong thing" to "we explicitly refuse to do the wrong thing".

That is, specifically, it expected that hg commands do not work in Phabricator if it can not determine the version of hg, so this is not a bug. Ignoring the setup warning might mean "we used to do Mercurial stuff but don't anymore, leaving us with some archived Mercurial repositories which we don't really need to look at, so it's okay that hg commands won't be able to run".

The version is strictly required because different versions of hg use different command syntax. If we can not determine which version of hg is installed, we can not run hg commands.

We haven't seen other users encounter this issue in several years.

No current plans to ever pursue this.

Herald rules are now always public, which possibly addresses the original issue.

We haven't seen more interest in this in several years.

This doesn't sound like a Phabricator problem.

I'm going to call this effectively resolved:

I'm pushing this here, yell if all your queries explode or what-have-ye.

I'd guess it's several days of work.

See Planning for information on planning and timelines.

One caveat about this is that it gets dicey if we implement T4280, since user-specified anchors could look like anything and could collide with anything. But we can cross that bridge when we come to it. This is an issue in general anyway, since two users can make comments with the exact same anchor in them.

If you believe you've found a bug in Phabricator, please follow the instructions in Contributing Bug Reports to file a report.

See also PHI41.

Did you consider increasing the "tablet" breakpoint above the size of an 11" macbook instead?

Yes. In Mercurial, branch heads may be "Open" or "Closed".

I'm going to merge this into T12963, which isn't exactly the same but overlaps this substantially. It's possible we'll pursue a more narrow "vacation review" mode eventually, but we'd want to finish T12963 first and make sure it didn't adequately address this problem on its own.