User Details
- User Since
- Oct 27 2015, 7:12 PM (477 w, 11 h)
- Availability
- Available
Jun 1 2021
Aug 13 2019
Apr 19 2019
May 6 2018
Feb 17 2018
The company I work for doesn't use Phabricator anymore. If I recall correctly the issue happens when an error occurs when creating the working copy. So DryDock create a copy 'copy-123' for example and then if an error occur (during the creation of the working copy for example can't fetch the repository), the build is stopped and the folder 'copy-123' is not deleted. DryDock will retry after 15s and create another copy 'copy-124'. So you can end up with millions of folders after a couple of hours.
Jan 6 2018
Jun 19 2017
Just out of curiosity, why Salt is not a candidate? I think it is very comparable to the others.
Jun 7 2017
May 12 2017
Apr 13 2017
I'd guess most people use the free Phacility plan because they need private repositories.
I don't think so because there are GitHub like solution that offer private repositories for free.
Apr 7 2017
Can't see the attached image: 500 Internal Server Error.
Is this really the new 'Needs review' icon or I have problem with fonts?
arc asked me why I skipped the tests. I provided one but I don't see it here.I got this error: Unable to establish a connection to any database host (while trying "phabricator_config"). All masters and replicas are completely unreachable.
Jan 26 2017
I think the problem you are describing has been already reported here. The users who reported it use a script to remove old tags. So you can do that.
Jan 22 2017
I think you can unlock yourself using the cli
Jan 16 2017
We also encountered this bug but after updating it disappeared.
Jan 3 2017
Have you forked phabricator ? Your commit sha (901e3051351dec3c041c683b6d1e718e587e2b4b) is not recognized in this install.
Dec 7 2016
Have you seen these warnings when creating your feature request?
Nov 26 2016
In /config/version/
Nov 1 2016
Oct 31 2016
Oct 26 2016
Oct 2 2016
You should read Contributing Bug Reports because your report is missing some informations like arcanist version. And I think that upstream is not supporting linters anymore.
Sep 29 2016
Sorry I though I was clear on how you could reproduce the bug. I will try again
Sorry I though I was clear on how you could reproduce the bug. I will try again
Applying a patch on the wrong repository.
I didn't suggest that. A solution can be to not apply that patch and inform the user about that.
Sep 21 2016
I have installed Phabricator from official documentation and get the same problem. I didn't create a bug report as I don't know the production steps. The problem occurred when I have upgraded Phabricator in July.
I have run to the same problem. I have restart the daemon multiple times to fix it.
I have run to the same problem. I have restart the daemon multiple times to fix it.
Sep 5 2016
What do you get if you run the same command with --trace flag ?
Sep 2 2016
Aug 31 2016
Aug 25 2016
Aug 21 2016
Reproductions steps :
Aug 19 2016
I also don't know how to reproduce the problem. I followed the guide found in T10246 to set up DryDock. I reported the bug hoping you could help me diagnosis the problem. How do you limit the number of working copies ?
Aug 18 2016
You should install arc. arc is the script in arcanist/bin/arc
My bad I didn't see the second comment by @chad. I know it is possible as @epriestley changed the language of this instance (see D16310#190724).
Does T8916 help?
Aug 2 2016
Jul 30 2016
You should check if the user has write access to the folder where the repositories are stored. It happened to me (I wasn't using Phabricator). I can clone because I have read to access but can't push because I didn't have write permission.
Jul 24 2016
I ran into the same issue and phabricator-ssh-hook.sh and its parent directory are owned by root and the script have 755 mode. The script was in /root/phabricator/ and vcs-user doesn't have access to that directory (because the /root directory is not accessible). I put the script in /etc/phabricator and it worked.
Jul 22 2016
It didn't work for me.
Jul 19 2016
Jul 17 2016
Fixed the commit's message
I can't fix the commit message :
Jul 12 2016
Jun 18 2016
May 25 2016
Mar 1 2016
Dec 24 2015
Apparently only failed build events are shown.