Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 495562

Summary: initial attempt to compare a file's changes consistently fails
Product: [ECD] Orion Reporter: Grant Gayed <grant_gayed>
Component: ClientAssignee: Project Inbox <orion.client-inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: major    
Priority: P3 CC: Carolyn_MacLeod, libingw
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Mac OS X   
Whiteboard:

Description Grant Gayed CLA 2016-06-06 15:42:56 EDT 
The following steps demonstrate the problem happening on the Git page, but it also happens on the Compare page:

- in your workspace change at least two files that come from the same repository
- go to the Git page
- expand one of items representing a changed file

- if you already have side-by-side diff mode selected then the problem will show:
  -> notice that only the RHS of the split shows message "fetching..."
  -> it never comes back
  -> collapse-then-reexpand that file: it now shows "fetching..." in both panes and works fine

- alternatively, if side-by-side compare was not pre-selected then toggle to it now
  -> the compare pane lays out again, and note that the LHS is empty (presumably the same root problem)
  -> refresh the page and you'll now see the first problem scenario happen for the first file that you expand
Comment 1 Carolyn MacLeod CLA 2016-06-07 12:45:29 EDT 
Confirmed on https://orion.eclipse.org/git/git-repository.html, but the same problem doesn't occur for me when self-hosting.
Comment 2 Grant Gayed CLA 2016-06-07 12:50:35 EDT 
I wonder if it's context-specific (eg.- the repo?), because it's now working for me on Beta3, though I don't see a recent change made to fix it.  It was failing for me there yesterday.
Comment 3 Grant Gayed CLA 2016-06-07 12:58:56 EDT 
I think it's failing at orion.eclipse.org because the version there is from June 3rd, while Beta3 is June 7th (as would be your self-hosted).  Still not sure what fixed it, but closing report regardless, will reopen if this happens again with a recent version.