Cool, let us know if you run into anything else.

Yeah, I upgraded my dev instance to Head which doesn't have this issue. Thanks!

(At the least, I can't reproduce these issues at HEAD.)

You're a few days out of date -- I believe both of these issues are fixed at HEAD. Can you upgrade and let me know if you're still seeing issues?

I can reproduce this on my dev install (Ubuntu 14.04.3 LTS, git 2.6, OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.3, OpenSSL 1.0.1f 6 Jan 2014, PHP 5.5.9-1ubuntu4.14):

$ git clone --depth 5  ssh://git@localhost:7422/diffusion/MNG
Cloning into 'MNG'...
remote: Counting objects: 3560, done.
remote: Compressing objects: 100% (2960/2960), done.
Receiving objects:  99% (3525/3560), 153.83 MiB | 102.55 MiB/s
<hang>

From a first glance it looks like the renderer may be the issue (tested the font in phabricator with figlet installed via homebrew):

Yes, exactly that.

Specifically, you're talking about this?

will the patch be reviewed and merged

@epriestley I don't think T9901 belongs here, as I've wanted to have arcanist "packaged", not whole Phabricator. And I've worked with PHP before, of I'm quite aware of how complex packaging and installation could be. But I'm not sure that applies to arcanist. Anyway, T4200#57593 has been red, so let me add my 2¢ relevant to my proposed approach (which is, after more thinking it through, to build and distribute an single-file self-contained arc executable along with every Phabricator instance).

I think we're going to work around this by changing our base config value to git:upstream, git:merge-base(origin/master) and decreeing that if you want to do this sort of dependent feature thing, you have to explicitly set child-feature's upstream to feature. arc feature does that automatically, so we might just encourage people to start using that.

sorry all our work are going through maniphest.

Are you referring to Maniphest, Differential, or Audit? What is your workflow now? This question is fairly vague.

That's the workflow I use, but I --amend "feature" when updating it.

pretty big rough edges for the workflows it intends to enable

What are these, specifically? Is this entire task moot?

Task creation slightly ahead of HEAD through maniphest.edit now hit essentially the exact same code as the web UI, and no longer appear to do this "[Reopened]" stuff.

This hasn't hit HEAD yet, but will be resolved indirectly as part of changes in connection with T9132 shortly as that rolls out.

See T4103 (or create a wiki page or dashboard).

I'm removing this "Create Project" workflow entirely in connection with T9132, obsoleting this task.

This is now fairly easy to implement and the race stuff isn't a problem anymore, but I'm not sure it's worthwhile from a product perspective. We could pursue these things fairly easily now:

See T4200.

I think this is mostly either resolved or obsoleted by "Email Commands" (Help → Email Commands in Maniphest). We also backed away from hashtags implying project associations, and that seems like it was a good call.

We haven't seen other use cases for this. OAuth or Nuance are more likely approaches from an upstream viewpoint.

Actually, you probably also don't really care about removing the comment event anyway, since it can't change policies and you can't comment on objects when creating them, and I think your listener doesn't actually end up doing anything special for the actions that are available? So this might be mostly moot anyway, but in an ideal world I'll get through the main "edit" event shortly too.

Quick update here: ApplicationEditor/EditEngine have caught up with this, so the current plan is to indirectly remove this event in at least some cases (currently: changes made from the "Comments" area) after the stable cut on Saturday. You can upgrade to this week's stable safely but we should make sure things are in a good place before you move beyond that.

Thank you Chad for your reply.

pretty big rough edges for the workflows it intends to enable

I think there are two issues here:

Again I attached strace to narrow down the problem further.

I think this is a problem only with the default font, it seems OK in other fonts:

I think the first SSH connection is still more expensive than several HTTP connections, and we can't easily just pool all traffic from a host over a single connection because a host may run multiple instances of Phabricator -- and we already built all the HTTP stuff anyway.

A quick update here, as per our analysis we came to know that the current issue was arised due to the elastic search related issue and we have fixed it. Now everything is working fine. :-)

Upgraded the phabricator search to elastic search using the following command.

Thank you!

In T9360#146722, @chad wrote:

DocumentPro is way better than Oblivious

In T4209#69927, @epriestley wrote:

Specifically, performance from the Diffusion browse views.

Unfortunately, given the lack of reproducible instructions and no other reports, there isn't anything currently for the upstream to do on this ticket except to ask whoever is having it, to provide us with more details. If we can't reproduce something, there isn't really much more we can do. The onus is on you to help with that effort.

Upgraded the phabricator search features to elasticsearch.

I have updated the phabricator tio recent version on Dec 2.