Bug Report (Needs Information)Bugs
ActivePublic

Watchers

  • This project does not have any watchers.

Details

Description

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.

Recent Activity

Aug 15 2017

epriestley moved T12534: Differential still appears in "responsible users" query after resigning as a reviewer from Backlog to Reviewer Rules on the Differential board.
Aug 15 2017, 5:54 PM · Bug Report (Needs Information), Differential

Aug 10 2017

epriestley removed a watcher for Bug Report (Needs Information): bingogo009.
Aug 10 2017, 1:17 PM
epriestley removed a watcher for Bug Report (Needs Information): rajuonraj.
Aug 10 2017, 1:17 PM

Aug 7 2017

bingogo009 added a watcher for Bug Report (Needs Information): bingogo009.
Aug 7 2017, 1:08 AM

Jul 27 2017

epriestley closed T12292: Diffusion commit details references HEAD -> master broken as Invalid.

We don't have reproduction steps for this and thus can't move forward.

Jul 27 2017, 4:26 PM · Bug Report (Needs Information)

Jun 7 2017

epriestley closed T12802: Schemata error after updating as Invalid.

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 7 2017, 10:44 PM · Bug Report (Needs Information)

Jun 6 2017

epriestley edited projects for T12802: Schemata error after updating, added: Bug Report (Needs Information); removed Bug Report.

I can't reproduce this. Here's what I tried:

Jun 6 2017, 10:28 AM · Bug Report (Needs Information)

Jun 5 2017

epriestley renamed T12796: Ambiguous URL rejection broke existing remarkup blocks with: [[ <ambigous URI> ... ]] from Ambiguous URL rejection broke some phriction pages to Ambiguous URL rejection broke existing remarkup blocks with: [[ <ambigous URI> ... ]] .
Jun 5 2017, 12:51 PM · Remarkup, Bug Report
epriestley added a comment to T12796: Ambiguous URL rejection broke existing remarkup blocks with: [[ <ambigous URI> ... ]] .

Thanks for updating your report with reproduction instructions, they were very helpful in reproducing and fixing the bug.

Jun 5 2017, 12:51 PM · Remarkup, Bug Report
epriestley added a revision to T12796: Ambiguous URL rejection broke existing remarkup blocks with: [[ <ambigous URI> ... ]] : D18076: Don't fatal when encountering [[ <bad URI > | ... ]].
Jun 5 2017, 12:48 PM · Remarkup, Bug Report
epriestley claimed T12796: Ambiguous URL rejection broke existing remarkup blocks with: [[ <ambigous URI> ... ]] .
Jun 5 2017, 12:39 PM · Remarkup, Bug Report
jbeck renamed T12796: Ambiguous URL rejection broke existing remarkup blocks with: [[ <ambigous URI> ... ]] from Ambiguous URL rejection broke some pages to Ambiguous URL rejection broke some phriction pages.
Jun 5 2017, 6:39 AM · Remarkup, Bug Report
jbeck added a comment to T12796: Ambiguous URL rejection broke existing remarkup blocks with: [[ <ambigous URI> ... ]] .

I have added some more details. Let me know if you need any more.

Jun 5 2017, 6:28 AM · Remarkup, Bug Report
jbeck updated the task description for T12796: Ambiguous URL rejection broke existing remarkup blocks with: [[ <ambigous URI> ... ]] .
Jun 5 2017, 6:28 AM · Remarkup, Bug Report
jbeck added a comment to T12796: Ambiguous URL rejection broke existing remarkup blocks with: [[ <ambigous URI> ... ]] .

Ok sorry, I will improve the report.

Jun 5 2017, 6:22 AM · Remarkup, Bug Report
chad edited projects for T12796: Ambiguous URL rejection broke existing remarkup blocks with: [[ <ambigous URI> ... ]] , added: Bug Report (Needs Information); removed Bug Report.
Jun 5 2017, 6:21 AM · Remarkup, Bug Report

Jun 2 2017

epriestley closed T12748: Duplicated comments on JIRA when differential revisions are linked to JIRA issues as Invalid.

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.

Jun 2 2017, 11:21 AM · Bug Report (Needs Information), Doorkeeper
epriestley closed T12764: Git clone suddenly timeouts on accounts with newly uploaded ssh keys as Invalid.

We don't know how to reproduce this, so we can't move forward, and haven't received more information in several days.

Jun 2 2017, 11:19 AM · Bug Report (Needs Information)
epriestley closed T12773: User image is found broken on migrating to the latest version of Phabricator. as Invalid.

We don't know how to reproduce this, and haven't received more information in several days.

Jun 2 2017, 11:18 AM · Bug Report (Needs Information)

May 30 2017

epriestley edited projects for T12748: Duplicated comments on JIRA when differential revisions are linked to JIRA issues, added: Bug Report (Needs Information); removed Bug Report.

Next steps:

May 30 2017, 6:14 PM · Bug Report (Needs Information), Doorkeeper
epriestley closed T12722: Auto-resolve with "Fix: T..." commit message should not reopen a closed bug as Invalid.

This doesn't appear to describe a bug in Phabricator.

May 30 2017, 6:08 PM · Bug Report (Needs Information)
epriestley closed T8109: Using 'arc feature' on mercurial repository gave an exception as Invalid.

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 30 2017, 6:07 PM · Bug Report (Needs Information), Mercurial, Arcanist

May 29 2017

chad edited projects for T12773: User image is found broken on migrating to the latest version of Phabricator., added: Bug Report (Needs Information); removed Bug Report.
May 29 2017, 1:53 PM · Bug Report (Needs Information)

May 28 2017

chad added a comment to T12764: Git clone suddenly timeouts on accounts with newly uploaded ssh keys.

@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 28 2017, 7:46 PM · Bug Report (Needs Information)
exp10r3r updated the task description for T12764: Git clone suddenly timeouts on accounts with newly uploaded ssh keys.
May 28 2017, 5:54 PM · Bug Report (Needs Information)

May 26 2017

chad added a comment to T12764: Git clone suddenly timeouts on accounts with newly uploaded ssh keys.

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 26 2017, 8:31 PM · Bug Report (Needs Information)
chad edited projects for T12764: Git clone suddenly timeouts on accounts with newly uploaded ssh keys, added: Bug Report (Needs Information); removed Bug Report.
May 26 2017, 8:30 PM · Bug Report (Needs Information)

May 19 2017

epriestley added a comment to T12722: Auto-resolve with "Fix: T..." commit message should not reopen a closed bug.

Currently, Fixes T123 in a commit message means this:

May 19 2017, 12:20 AM · Bug Report (Needs Information)
chad added a comment to T12722: Auto-resolve with "Fix: T..." commit message should not reopen a closed bug.

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.

May 19 2017, 12:19 AM · Bug Report (Needs Information)
chad added a comment to T12722: Auto-resolve with "Fix: T..." commit message should not reopen a closed bug.

It still doesn't sound like a bug to me, or maybe more specifically, understand what you expect the upstream to fix.

May 19 2017, 12:15 AM · Bug Report (Needs Information)

May 18 2017

zhiyuchen updated the task description for T12722: Auto-resolve with "Fix: T..." commit message should not reopen a closed bug.
May 18 2017, 9:57 PM · Bug Report (Needs Information)
zhiyuchen added a comment to T12722: Auto-resolve with "Fix: T..." commit message should not reopen a closed bug.

@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...."

May 18 2017, 9:56 PM · Bug Report (Needs Information)
avivey added a comment to T12722: Auto-resolve with "Fix: T..." commit message should not reopen a closed bug.

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.

May 18 2017, 7:30 PM · Bug Report (Needs Information)
zhiyuchen updated subscribers of T12722: Auto-resolve with "Fix: T..." commit message should not reopen a closed bug.

@avivey I updated description to include version info, repeatable and steps to reproduce, is there anything else you guys need?

May 18 2017, 6:50 PM · Bug Report (Needs Information)
avivey edited projects for T12722: Auto-resolve with "Fix: T..." commit message should not reopen a closed bug, added: Bug Report (Needs Information); removed Bug Report.
May 18 2017, 5:09 PM · Bug Report (Needs Information)

May 15 2017

epriestley added a revision to T12710: Project "Profile" and "Subproject" tabs now require members/watchers, but do not load them: D17882: Add required needMembers/needWatchers calls to Project Profile/Subprojects tabs.
May 15 2017, 1:38 PM · Projects, Bug Report
epriestley added a comment to T12710: Project "Profile" and "Subproject" tabs now require members/watchers, but do not load them.

I'll just ship up the "unbreak" diff, and you can either counter-diff me or figure out something else.

May 15 2017, 1:36 PM · Projects, Bug Report
epriestley updated subscribers of T12710: Project "Profile" and "Subproject" tabs now require members/watchers, but do not load them.

I think more narrow reproduction instructions are:

May 15 2017, 1:35 PM · Projects, Bug Report
mrthomasbrix added a comment to T12710: Project "Profile" and "Subproject" tabs now require members/watchers, but do not load them.

Yes on the Almanac project profile.

May 15 2017, 11:38 AM · Projects, Bug Report
epriestley edited projects for T12710: Project "Profile" and "Subproject" tabs now require members/watchers, but do not load them, added: Bug Report (Needs Information); removed Bug Report.
May 15 2017, 11:12 AM · Projects, Bug Report

May 8 2017

cxzzero added a comment to T12687: When submitting an arc diff, svn diff or updating a revision a Parse Exception ocurrs in Windows.

Thanks, let me check that task and I tell you.

May 8 2017, 7:18 PM · Windows, Bug Report (Needs Information)
avivey added a comment to T12687: When submitting an arc diff, svn diff or updating a revision a Parse Exception ocurrs in Windows.

This might be a variant of T2465. There's some workaround described there that might help.

May 8 2017, 5:59 PM · Windows, Bug Report (Needs Information)
avivey added a project to T12687: When submitting an arc diff, svn diff or updating a revision a Parse Exception ocurrs in Windows: Windows.
May 8 2017, 5:56 PM · Windows, Bug Report (Needs Information)
cxzzero added a comment to T12687: When submitting an arc diff, svn diff or updating a revision a Parse Exception ocurrs in Windows.
  • 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
May 8 2017, 5:47 PM · Windows, Bug Report (Needs Information)
chad added a comment to T12687: When submitting an arc diff, svn diff or updating a revision a Parse Exception ocurrs in Windows.

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?

May 8 2017, 5:38 PM · Windows, Bug Report (Needs Information)
chad edited projects for T12687: When submitting an arc diff, svn diff or updating a revision a Parse Exception ocurrs in Windows, added: Bug Report (Needs Information); removed Bug Report.
May 8 2017, 5:36 PM · Windows, Bug Report (Needs Information)

Apr 23 2017

arrowd added a comment to T12521: "(Exception) Expected nonempty 'cmds' specification!" when trying to clone or pull mercurial repository.

After fiddling with some more upgrades, I started to get

Apr 23 2017, 6:01 PM · Bug Report (Needs Information)
arrowd added a comment to T12521: "(Exception) Expected nonempty 'cmds' specification!" when trying to clone or pull mercurial repository.

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 23 2017, 5:32 PM · Bug Report (Needs Information)

Apr 13 2017

cspeckmim added a project to T8109: Using 'arc feature' on mercurial repository gave an exception: Bug Report (Needs Information).
Apr 13 2017, 5:48 PM · Bug Report (Needs Information), Mercurial, Arcanist

Apr 11 2017

epriestley added a comment to T12534: Differential still appears in "responsible users" query after resigning as a reviewer.

This is currently expected, although we could consider changing it.

Apr 11 2017, 11:29 AM · Bug Report (Needs Information), Differential