Last modified: 2013-06-27 20:04:57 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T42021, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 40021 - Blank page on comparing a file over two commits
Blank page on comparing a file over two commits
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Git/Gerrit (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
https://gerrit.wikimedia.org/r/#/c/89...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-05 19:45 UTC by Mark Holmquist
Modified: 2013-06-27 20:04 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
Screenshot of the issue, and JavaScript error in the console, not logged (58.61 KB, image/png)
2012-12-30 20:22 UTC, Jesús Martínez Novo (Ciencia Al Poder)
Details

Description Mark Holmquist 2012-09-05 19:45:36 UTC
I tried to compare a file, with several changes, across patchsets 10 and 11. That didn't work.

See the link. I get essentially a blank page, the menus indicate that Gerrit thinks I may be in a search result page or something--definitely not a diff.

hashar suggested that I should uncheck the syntax colouring option, but that changed it into a server error. Very annoying.

Dunno what's happening here, but clearly it's not good.
Comment 1 Chad H. 2012-09-11 18:21:50 UTC
Worksforme -- what browser are you using?
Comment 2 Jesús Martínez Novo (Ciencia Al Poder) 2012-09-11 18:29:07 UTC
I have the same problem. Blank page.

The error console says:
Error: uncaught exception: Class$fRc: Array index 94 out of range

Strange enough: No source file.

Browser: Mozilla Firefox 15.0.1 under Windows XP
Comment 3 Andre Klapper 2012-12-21 17:23:13 UTC
I get for that URL:
Timestamp: 12/21/2012 06:22:46 PM
Error: uncaught exception: Class$ArrayIndexOutOfBoundsException: Array index 94 out of range
Comment 4 T. Gries 2012-12-30 20:11:49 UTC
We just discovered that one possible reason can be:

* there are unpublished (draft) comments. Only the commenter can see them, other users get "Internal server error" from gerrit.
Comment 5 Jesús Martínez Novo (Ciencia Al Poder) 2012-12-30 20:13:22 UTC
Another report:

https://gerrit.wikimedia.org/r/#/c/3925/6..7/RSS.php

Discussed as happened on IRC http://bots.wmflabs.org/~wm-bot/logs/%23mediawiki/20121230.txt
Comment 6 T. Gries 2012-12-30 20:16:02 UTC
for me https://gerrit.wikimedia.org/r/#/c/3925/6..7/RSS.php works on Firefox 17.0.1 when I am logged in to gerrit.
Comment 7 Jesús Martínez Novo (Ciencia Al Poder) 2012-12-30 20:22:44 UTC
Created attachment 11568 [details]
Screenshot of the issue, and JavaScript error in the console, not logged

(In reply to comment #6)
> for me https://gerrit.wikimedia.org/r/#/c/3925/6..7/RSS.php works on Firefox
> 17.0.1 when I am logged in to gerrit.

Attached screenshot of the error, done wile not logged in (on a separate Firefox profile used for testing), but the error also appears on my main instance when logged in. Firefox 17.0.1
Comment 8 T. Gries 2012-12-30 20:26:27 UTC
(In reply to comment #7)
> Created attachment 11568 [details]
> Screenshot of the issue, and JavaScript error in the console, not logged
> 
> (In reply to comment #6)
> > for me https://gerrit.wikimedia.org/r/#/c/3925/6..7/RSS.php works on Firefox
> > 17.0.1 when I am logged in to gerrit.
> 
> Attached screenshot of the error, done wile not logged in (on a separate
> Firefox profile used for testing), but the error also appears on my main
> instance when logged in. Firefox 17.0.1

I confirm your observation.
Comment 9 Valerie Juarez 2013-02-19 23:16:53 UTC
I can confirm this bug for FF18 and IE9. The error messages noted above (in the screenshot and #c3) are the same in each browser.
Comment 10 Chad H. 2013-06-27 16:22:03 UTC
I believe this has been fixed.
Comment 11 T. Gries 2013-06-27 20:04:57 UTC
looks to be fixed, yes, let#s closed this.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links