Actually, the problem seems to be in the system configuration. There a hard limit on open file descriptor ( which limits mysqld to 214 connections.

After setting max_connections=1500 , the problem still happens some hours after running the instance.

I can confirm that this bug also happen on a local install with a few users (around 15)

Note: this is only to log informations and try to reproduce the issue, with other user who see this bug, is it okay if I keep using this ticket ?

I'm reproducing this issue on a standard installation. As I said, here is our configuration

I actually encouter the same problem. Setting autoclose on master only fixed it.

Indeed, it's fixed ! Thanks

@chad: Ok, it makes sense, but in github, the layout is a small fixed one, not a full page one, thus the information is much more compact (at least on a 24" screen) and the "Author" is referenced under the issue title.

@chad, don't worry, I understood that it's important for you to have clear input from users and that's why I apologize for being unclear with my request. Moreover, as you say, this is pretty superficial and we can maintain it on our local install. But as it was the general return from our users (unintuitive UI), I thought it could be reported to upstream.

Mainly because this is one of the main component of a task (ie, what defines a task). But actually, this is something which could be customized on our side. Sorry for bothering you and being unclear about the request. I think you can close this task.

Sorry, I read the "Describing Root Problem" and I thought that explaining the main problem (not intuitive for users and lack of visibility for Assigned to and Authored By) was sufficient.
The problem is that users ( at least ours) want to find all essential information (and assigned to seems to be an essential information) in the same place by taking a quick look at the task such as for priority and status.

Ok seems reasonnable :) Thanks for the answer !

I can confirm this behavior. Is there any way to fix that ?

This problem is probably the same as the one in task T10120. This is probably related to caching since clearing the cache restore the functionnality (at least for some times).
However, in our case, we have a regular httpd server without any mods installed.
Do you have any ideas of how we could debug that ?

Thanks for the quick fix !

Thanks !

Ok, thanks, note that this problem is probably the same as this one: T7260
But it seems to be easily reproducible with linux repo.

Thanks for the quick fix !

Hi chad,
We ran into this bug because a colleague use it and couldn't display project tasks.

Great, it works like a charm !

I'm hitting the same problem using Chrome (Version 41.0.2272.89 (64-bit)).
However when using firefox, I do not have this problem so it seems to be browser related.

@epriestley, Thanks, of course, adding any file to the next commit solves the problem.
By the way, it is a not a high priority bug since it does not broke the interface.

@wakes, Yes I'm reproducing the issue on a local install.
Here is the configuration:
Distrib:

Centos7-64

My bad, the phabricator commit is the following one: f59ebf4c09598e5f02657a4037c822b64a306646.

On a local install, we are also getting this error.
phab : f4d47d93fd8a56f918e4cfa72bf96d6997955a8d
libphutil: 0fa7efbf09d75b7803ef54bd6c72ee3c69a964e4