A bug report that is not currently able to be reproduced by the upstream. Either based on missing full steps to reproduce the issue or other variables outside of our control. For more information, see https://secure.phabricator.com/book/phabcontrib/article/bug_reports/#unreproducible-problems.
Jan 13 2020
If you believe you've found a bug in Phabricator, please report it by creating a new thread on Discourse.
Jan 8 2020
Last follow-up -- no, it was not a custom policy. The log of changes to the Project configuration show that the original setting for the edit policy was indeed "Project Members", which seems to indicate that Phabricator was incorrectly preventing new members from editing the Project.
I was unable to reproduce this with a new Project, which makes me suspect the problem isn't a bug in Phabricator. I suspect the Project that was not editable *actually* had a Custom policy with specific users added to it, rather than a "Project Members" policy.
I ran into this issue today as well. The context was a Project created by a regular user a few months back. He added himself and one other user to the Project. He also set the edit policy for the Project to be "Project Members." A few months later, a couple of other users were added to the Project, but neither of them could edit the Project (all links in the "Manage" UI were disabled, can't create milestones, etc.). The users who were in the group when the edit policy was set were still able to manage the group. One of them had to change the edit policy because the newer members of the group could not.
Jul 12 2019
Mar 23 2019
Just ran into this issue on a freshly installed Ubuntu 16.04 docker container.
Actually it's just the package phpX.Y-xml what is missing.
In my case it was php7.2 so all I needed to do was:
sudo apt install php7.2-xml
(No extra repositories needed...)
Feb 23 2019
We no longer offer support for this kind of problem (that technically has reproduction steps, but is sufficiently involved to reproduce that no one has time to follow them, e.g. build a new server from scratch with assorted specific software versions).
Feb 16 2019
This report is generally unclear / hard to reproduce / unusual so I'm not sure how to move forward. It's likely mooted by D20181.
Dec 13 2018
If you want me to look at something, file a report on Discourse with reproduction steps that I can follow to reproduce the issue. I don't need any other discussion or context. I do need working reproduction steps.
@epriestley I have seen you working on Mercurial stuff. Can you take a look at my findings above?
Dec 4 2018
Ok, I think the problem is here: https://github.com/phacility/phabricator/blob/master/src/applications/diffusion/controller/DiffusionServeController.php#L816
I've managed to find the root of the problem, I think. Here is the actual error message that arises somwhere deep in Phabricator and then gets cut turning into non-informative ** unknown exception encountered, please report by visiting:
I still having this problem. @rafaelrabeloit, had you chance to fix or work-around this?
Oct 2 2018
No clue how to reproduce this.
Sep 27 2018
This doesn't seem actionable and is likely mooted by T13098.
Aug 10 2018
Apr 4 2018
i met the same issue, and i found the root cause was the OpenSSH upstream issue.
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.
Feb 13 2018
I'm unable to reproduce this by following the instructions provided, at least after changes in T13073. Here's what I did:
Jan 4 2018
This is possibly connected to T9548 but we don't know how to reproduce this and can't fix issues we can't reproduce.
Dec 13 2017
Aug 15 2017
Aug 10 2017
Aug 7 2017
Jul 27 2017
We don't have reproduction steps for this and thus can't move forward.
Jun 7 2017
We haven't received the information we need to move forward, so I'm going to close this. Feel free to follow up here or open a new task if you're able to provide detailed reproduction instructions we can use to reproduce the issue locally.
Jun 6 2017
I can't reproduce this. Here's what I tried:
Jun 5 2017
Thanks for updating your report with reproduction instructions, they were very helpful in reproducing and fixing the bug.
I have added some more details. Let me know if you need any more.
Ok sorry, I will improve the report.
Jun 2 2017
We haven't received more information on this, so we don't know how to reproduce it and can't move forward. Feel free to file a new issue in the future with complete reproduction steps, per above.
We don't know how to reproduce this, so we can't move forward, and haven't received more information in several days.
We don't know how to reproduce this, and haven't received more information in several days.
May 30 2017
This doesn't appear to describe a bug in Phabricator.
I'm just going to nuke this since there's no repro. This workflow has also been rewritten on the experimental branch and the specific error encountered here should now be impossible.
May 29 2017
May 28 2017
@exp10r3r you still need to provide reproduction steps. Based on the ones provided, I cannot reproduce any issue using a new/clean install on Phacility or locally. That doesn't mean there isn't a bug to fix, but without the specifics needed to observe and troubleshoot the issue, we have no idea where to start or what to look for. Because we provide support for free, it's on report submitters to fill in all the details needed here. We can't assist with that. No other install is reporting this issue, so it's unlikely due to any change from the upstream.
May 26 2017
Specifically, reproduction steps are a set of complete, detailed steps we can follow and see the same issue you are seeing locally. Bonus if you've taken a new, clean image and reproduced the issue.
May 19 2017
Currently, Fixes T123 in a commit message means this: