Page MenuHomePhabricator
Create Task
Maniphest T12292

Diffusion commit details references HEAD -> master broken
Closed, InvalidPublic
Actions

Description

Running Phabricator 3e10f69570c0eb007f85917e16a249ea70d2dda8 from the stable branch.

When I look at a the latest commit in a Diffusion, in the Details window I see a References HEAD -> master with a link which looks like this https://dev.marples.name/source/parpd/browse/HEAD%2520-%253E%2520master/;74045ea881357edd2d29fd15ea55f236bc289446
You can currently see this in action here.
Clicking it shows what looks like a snapshot of the files at this commit, but then looks like I'm on a branch called HEAD -> master. Clicking this then gives this error

Unexpected object type from `git cat-file`: HEAD -> master missing

I notice that on this site, the Reference HEAD -> master link on the latest commit looks like this (just picking the current latest commit) https://secure.phabricator.com/rP9f3cde4db7654499c1ed565fbf048b8e8710f70a

Event Timeline

rsmarples created this task.Feb 19 2017, 10:18 PM
chad added a subscriber: chad.Feb 19 2017, 11:14 PM

Please provide reproduction steps, we don't accept bug reports that ask us to go look at their server.

rsmarples added a comment.Feb 20 2017, 9:30 AM
  1. Install Phabricator at the version noted above.
  2. Import a GIT repository via observing a URI.
  3. Note the reference HEAD -> master link broken on latest commit.

For reference, I'm using PHP-7.1.2 and Git 2.11.1

Attached is a screenshot to show the problem.

phab_master_head_link2.png (727×937 px, 110 KB)

You can see that Firefox shows the broken link at the bottom of the window.
I drew an arrow showing where the link is to be explicit.

chad added a comment.EditedFeb 22 2017, 9:22 PM

Hi @rsmarples, unfortunately I don't know how to reproduce this based on your steps provided. Specifically, I do not see a broken "reference" link in the details of the commit. Do you know what additional steps I can take to see this bug locally? Everything looks formatted fine?

chad added a subscriber: epriestley.Feb 22 2017, 9:24 PM

We require all bug reports provide complete reproduction steps. The main reason is so that anyone can follow and reproduce the bug in a local environment. Skipping details makes it difficult for most (or anyone but @epriestley) people to provide you with help.

chad edited projects, added Bug Report (Needs Information); removed Bug Report.Feb 22 2017, 9:25 PM
chad added a comment.Feb 22 2017, 9:43 PM

Feel free to use a Phacility Test Instance and record your steps, thanks!

rsmarples added a comment.Mar 16 2017, 12:50 AM

Try as I might, I cannot reproduce this in a test instance hosted by yourselves.
The on screen description is the same (HEAD -> master), but the actual URL it goes to is different compared to my instance, even with the same repositories loaded.

Is there an informational screen in Phabricator to report PHP and/or GIT versions in use? At this point I'm guessing it's an environment issue, but unsure where.

Please note this is very low priority, it's just a minor niggle I have.

epriestley closed this task as Invalid.Jul 27 2017, 4:26 PM

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

Phabricator · Built by Phacility