Yeah I think the need for corporate users to hide things from their enemies is probably outside of our control. Just try to find lots of bugs with it.

Oops -- I assumed that package was someone testing things since every other object that has ever been hidden has been and ran bin/policy unlock without examining it, but it's actually a legitimate package. I think I put it back the way it was.

You're currently the only user we're aware of who experiences this -- have you tried changing your IDE so it, e.g., only polls git while in the foreground?

See also T4788 for some other followup work.

Because of the intermediary join to the edge table I wasn't actually able to get it working without HAVING either, but D16340 should fix the underlying issue here.

I believe the best way to construct these queries is like this:

I'm planning to make these changes:

A subproblem here is perhaps that Owners should have a "Can Create Packages" policy.

I'm not exactly sure what this is asking for -- it sounds like you just want a more convenient way to post a comment asking revision authors to "Please re-run the optional tests."?

I think you're free to fiddle -- there are some more adjustments and things, but nothing too significant. I think the only other really CSS-ish thing is that if you search for events in a specific range (July 5-7) on a calendar view, I'd like to make it clear which days your query covers.

This is working as intended.

After D16333 there's still a tiny amount of unique spelling correction code in Arcanist, but it's just calling into libphutil and part of code duplication which would be better resolved elsewhere (like T7487).

For completeness, I'll also drop a mention of T5024 here, although I'm not yet sure how the two might tie together.

We do not currently support RTL languages. You can follow T5267 for progress on internationalizing Phabricator, but we currently expect to support LTR latin languages first and it may be some time before we support RTL languages.

You are in the wrong place -- it looks like you mean to be on Uber's internal install of Phabricator, but this is the public upstream install of Phabricator.

Oh, I forgot to mention this but T10333 (groups within columns) is another possible attack here, and one I definitely intend to implement regardless of other work and outcomes (e.g., T5474) since I think it stands on its own and is already well-justified by confusion with priority-ordered boards. T10333#158767 has the ASCII-art mock:

Thanks for the report, and for providing detailed reproduction steps.

Phlux should probably be on the chopping block too since Almanac pretty much obsoleted it in Phacility production.

Here's an effort to collect use cases for the hooks I plan to break or replace:

Concretely, I think this breaks down as a mixture of modernizations and new code:

Changes connected to T8116 implement the initial server-side version of this. It's still very skeletal, but we probably need to make some client changes to move forward. In particular, the next object to implement is probably Signature, but signature algorithms should live in the client since the client will need to be able to verify signatures.

I'm just going to consolidate this into T5055, I think they're pretty much the same task at this point.

Given my description, what other behavior do you think it might have?

(T11357 is a companion issue for Files.)

D16323 uses <input type="text" pattern="\d*" />, which appears to have the best behavior.

On iOS 9.2 in the simulator, <input type="number" /> gives you this keyboard:

Oh, there's a "Toggle Software Keyboard" option that I somehow disabled.

On iPhone Simulator, the behavior of <input type="number" /> appears to be "draw the keyboard for 1 frame and then immediately hide it".

Offhand, do you know if <input type="number" /> has the desired behavior on your device?