I've been running into the same issue for a while now. Using the Default Policy set to Subscribers for Files works well when adding files to Phriction pages and Maniphest tickets. However, when adding binary files as part of a Diff the creator of that Diff needs to change each files permissions by hand before a reviewer can download the Diff. Moreover, this needs to be repeated for every new version of that Diff.

Your Github repository is a nice reference. I will do the same for T9797

To clarify: I certainly don't this dependency to be simply swapped for another dependency. Also having 2 server implementations isn't desirable either. I can't judge whether a PHP implementation can challenge the NodeJS implementation because I'm lacking the experience in PHP.

I think it would be nice to have out-of-the-box support for the clang linter.

I'd really like to see this happen. So far I haven't used Aphlict simply because I don't want to manage the extra dependency.

In D14430#163129, @avivey wrote:

Does this mean it is likely to break in a month?

Well, it means a developer must use the HEAD of the git repository instead of the latest tagged version.

As in, the installation instructions are "clone HEAD of some repo"?
This might sound strange, but these instructions are more than I'd expect users to handle (Users are repeatedly baffled by "run 'npm install jshint'". I wish I was exaggerating).

Also, if there's no official version that supports this code, they can decide to change their api, making stop working.

Interesting. I will add some additional info regarding this issue to the instructions.

In D14430#162778, @avivey wrote:

As per https://secure.phabricator.com/book/phabcontrib/article/contributing_code/, you should file a task for this change before you can get any attention.

Thanks for the pointer, I created the appropriate tasks: T9796 and T9797

Does this mean it is likely to break in a month?

Well, it means a developer must use the HEAD of the git repository instead of the latest tagged version.

Can you put this into the test runner code, so that configuration is easier for users?

It is already in the file's documentation, what else are you referring to?

• Make ExUnitTestEngine handle Mix projects in subdirectories

• Allow linting from a parent directory
• Fix linting error

• Allow linting from a parent directory

I should note that I'm not used to working with PHP, so feel free to criticize. I tried to stay close to the other unit and lint classes.

Fixed local lessc unit test issue