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.
Wed, Jun 7
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.
Tue, Jun 6
I can't reproduce this. Here's what I tried:
Mon, Jun 5
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.
Fri, Jun 2
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.
Tue, May 30
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.
Mon, May 29
Sun, May 28
@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.
Fri, May 26
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 reproduce the issue.
May 19 2017
Currently, Fixes T123 in a commit message means this:
Basically, you're choosing to use a singular task status to track the various lifetime stages of a bug through multiple branches, which isn't what we intended that field for. It's just as easy to expect QA to want to re-confirm the bug is fixed in master as it is your workflow. I think you should track QA in a custom field.
It still doesn't sound like a bug to me, or maybe more specifically, understand what you expect the upstream to fix.
May 18 2017
@avivey If you follow the steps in my description, you should be able to reproduce the problem. I'm also attaching a screenshot which indicates that a maniphest was reopened from "Accepted" to "Resolved" twice because the merge commit msg also contains the original commit msg "... fix T...."
We need to have enough information to actually see the problem happening, so we can figure out what's wrong, and maybe even test a fix.
@avivey I updated description to include version info, repeatable and steps to reproduce, is there anything else you guys need?
May 15 2017
I'll just ship up the "unbreak" diff, and you can either counter-diff me or figure out something else.
I think more narrow reproduction instructions are:
Yes on the Almanac project profile.
May 8 2017
Thanks, let me check that task and I tell you.
This might be a variant of T2465. There's some workaround described there that might help.
- Windows version is Windows 7 with latest updates,
- PHP version 5.6.13,
- svn, version 1.9.4 (r1740329), compiled Apr 24 2016, 15:40:35 on x86-microsoft-windows
- arcanist version mentioned above
This is a little light on reproduction steps. Can you give us more information such as the version information on Windows, SVN, local arcanist, if you attempted reproduction against a clean Phacility instance or against SVNTest here?
Apr 23 2017
After fiddling with some more upgrades, I started to get
Just faced that problem on my micro hosting. I've updated some software and then started to get the same error as OP when cloning/pulling/pushing mercurial repos. Here is the list of software, that got updated back then: https://paste.kde.org/pqelvuhjf
Apr 13 2017
Apr 11 2017
This is currently expected, although we could consider changing it.
When I turn on bucketing, I can't see it actually. Although I do have a lot of diffs, so it could have overheated.
Where does it go when you turn on bucketing?