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.
Fri, May 19
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.
Thu, May 18
@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?
Mon, May 15
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.
Mon, May 8
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?
Sun, Apr 23
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?
Apr 9 2017
This still needs complete reproduction steps to be accepted into the upstream. My suggestion is find another VM and load out what you expect the issue is with, and give us those details. Right now it sounds like you're just guessing and that's outside of what we expect when following Contributing Bug Reports. See https://secure.phabricator.com/book/phabcontrib/article/reproduction_steps/ if you need more guidance on providing these steps.
Apr 7 2017
We don't know how to reproduce this and can't move forward.
We don't know how to reproduce this.
That's expected, and not a bug. "Blocking" is currently a top-level status. When a reviewer becomes "Rejecting", they are no longer "Blocking". This doesn't matter in terms of the workflow, because both "Rejecting" and "Blocking" prevent a revision from transitioning to "Accepted".
I've repeated this again, taking some screen dumps. This time I did it on a Phacility hosted instance, instead of on our self-hosted instance.
Apr 6 2017
Mar 29 2017
@dainysunil you need to provide full instructions to reproduce this issue in an untainted environment.
@chad -we tried the upgrade once again .. but the issue is still there
My only guess here is something is corrupt, incomplete, or not upgraded properly. I don't see anything on our side that would lead to this state.
If you believe those are the full, complete steps to reproduce the issue then please take the time and launch a clean test environment and follow the steps and let us know if they are complete.
We don't accept bug reports without reproduction steps.
Please find the image with upgrade branch. While upgrading the phabricator from this branch we found this error. Please check this upgrade to reproduce the error.
Mar 28 2017
If you believe you've found a bug in Phabricator, we need all the information discussed in Contributing Bug Reports to move forward. Specifically:
Mar 27 2017
We need reproduction steps to move forward. See Providing Reproduction Steps.
Mar 22 2017
Thanks @chad for the help and motivation~