D16744 should also improve SSH performance slightly, with a larger impact on larger instances.

This may have been the "MaxStartups" directive in sshd; if so, a partial fix is currently deployed (raising the limit on application load balancers) and a more comprehensive fix will go out tomorrow morning (also raising the limit on repository shards).

@epriestley, sure, I was not (intentionally) trying to be against subproject columns per se. I think they are a good way forward for making subprojects more usable.

I have pretty much the same "Status 126" issue on an Ubuntu 16.04 box with the latest openssh packages installed, following the instructions provided and modiying them for naming requirements. I'm running Phabricator on Nginx with PHP-FPM.

@epriestley , do you have an example of how one can use 'arc call-conduit phriction.query' ?

@iamvoid I think that you don't really understand the meaning of the term "onboarding" - it refers to a process that occurs after evaluation. Thus, you comment doesn't make sense, in my opinion. Any quality product or project should have a solid documentation, including parts, covering an onboarding process. The existence of the document above supports my argument.

In J766#294, @ablekh wrote:

The onboarding would be much easier, if Phabricator would offer a clear and detailed single document, describing and explaining the full Phabricator-based development process (along with rationale, advantages and disadvantages at each step). Something similar to this nice post, but more clear and more comprehensive.

Awesome, thanks for following up. Let us know if you run into anything else!

I do not plan to ever let you reorder milestones.

my current view is basically that the official subprojects implementation only makes this much more clunky and restricts some parts of it, rather than moves it forward. As it is, the current subproject implementation doesn't seem to do much else than make a couple of links appear, and restrict the usage of some features (tagging and project membership handling are changed/restricted, at least).

We deployed D16714 and reran one of the failing tasks -- it completed cleanly as expected. Thanks!

For reference, http://phacility.com/ is a Phabricator application itself, so think all the tools are available.

I presume you meant to ask this question in Ponder, otherwise please see Contributing Feature Requests for what information is required in a feature request. Generally, we do not provide support for building applications/plugins/extensions against Phabricator.

I'm going to merge this into T11357. We can provide a "Delete File Data" transaction type when we implement a third-generation file.edit API.

Is this a dup of (fixed) T10746?

In T11669#197945, @chad wrote:

It's always felt like 10% unpredictable to me, but I haven't tried it in a while.

Among other issues, arrows are, e.g., ambiguous in this case:

...
|          |   |   B    |
+----------+   +--------+
+----------+  
|    A     |   +--------+
|          |   |   C    |
|          |   +--------+
+----------+
+----------+   +--------+
|          |   |   D    |
...

If you click "Move Right" on "Panel A", does it move between panels B and C or between panels C and D?

This has been live for about two months without any substantive issues arising.

I don't plan to implement the rest of the feature request. Assuming drag and drop works correctly, I think this operation (reordering panels) is rare enough that using it is reasonable without introducing the additional complexity of duplicate controls.

It should show a pretty clear preview of what it's going to do before you drop, so I'm not sure how it could be unpredictable? I wasn't able to identify any weird/surprising behavior when I tried to reproduce this.

It's always felt like 10% unpredictable to me, but I haven't tried it in a while.

In T11775#197941, @epriestley wrote:

even sometime seems to me not properly working

If this isn't working properly, please file a bug report with complete reproduction steps we can use to reproduce the issue. See Contributing Bug Reports.

even sometime seems to me not properly working

I wasn't actually able to reproduce this -- were you, @chad?

Pagination isn't quite as simple as I'd remembered. Specifically, we do not expose internal pagination cursors to viewers today because doing so permits an information discovery attack that goes like this:

Ok, thanks for the explanation!

Broadly, I think the two above comments are expressing a mixture of two ideas:

The proposed behavior (no subproject columns) means that tasks could be in multiple different columns at different levels, since they'd be draggable normally on each workboard:

T11774 wants a "delete file data" transaction, which is reasonable.

This is working as intended, and not a bug. Administrators can not bypass policies. See the User Guide: Account Roles documentation:

The feeling now is that by assigning a task to a subproject it "dissapears", since it cannot be tracked in the workboard with milestones of the parent project, and is two extra clicks away: Subprojects > Mac OS X.

I think this behavior is very good

This is also a potential problem in the general case, although the general case of this is very rare.

Broadly, most applications can execute Spaces queries cheaply by querying ... AND spacePHID IN (<list of spaces the viewer can see>) when Spaces are configured, which is efficient until some install decides to create 30,000 Spaces for some reason.

The reporting user configured debug.time-limit to get a stack, which confirms this is a Feed issue:

Here are slightly cleaned-up recent timeouts from the logs:

yeah this is tricky since Conpherence has it's own separate notification channel. I was hoping to just pop these in with standard Mailtags, which sort of works, but is also sort of confusing.

[ Ok ] [ Try Again ]

I'm pretty sure you're filing this ticket in the wrong place. We don't have any lyrics.

I'm going to close this since things seem to have at least mostly worked and installs have had a couple of weeks to yell at us if we blew anything major up, but let us know if anyone runs into further issues.

This is a global javascript behavior, it's not tied to accounts or policy access.

Have the same issue.
Somehow it depends on the user accounts. Some users can do it, some can not. Any idea what userconfig can be causing that?

As said in Q501 it will be useful to have some components (e.g. an administrative panel) that appear on top of all the dashboards.