https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
Andre Klapper changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
--- Comment #22 from Siebrand ---
Should this be marked dupe of bug 45267 ?
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
Wikibugs
https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
Siebrand changed:
What|Removed |Added
CC||s.mazel...@xs4all.nl
--- Comment #21 from S
https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
Chad H. changed:
What|Removed |Added
Priority|High|Highest
Severity|normal
https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
--- Comment #19 from Gabriel Wicke ---
Just hit this issue again on a random patch page. Logging out twice helped for
the moment, as did ?dbg=1.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list
https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
--- Comment #18 from Chad H. ---
We tried flushing all the on-disk caches this morning, doesn't seem to have
helped :\
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_
https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
--- Comment #17 from Matthew Flaschen ---
I did the following:
1. Deleted the GerritAccount cookie (de facto logging myself out), which is the
only cookie.
2. Used the Firefox "Clear Recent History" dialog, selecting "Everything" (no
time cons
https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
--- Comment #16 from Liangent ---
(In reply to comment #14)
> (In reply to comment #9)
> > We just had a report that logging out and in again was required twice on
> > Firefox 20. Then it worked again.
> >
> > (When logged out, the change load
https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
--- Comment #15 from Liangent ---
(In reply to comment #14)
> (In reply to comment #9)
> > We just had a report that logging out and in again was required twice on
> > Firefox 20. Then it worked again.
> >
> > (When logged out, the change load
https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
--- Comment #14 from Liangent ---
(In reply to comment #9)
> We just had a report that logging out and in again was required twice on
> Firefox 20. Then it worked again.
>
> (When logged out, the change loaded without any problem)
Well doing
https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
--- Comment #13 from Liangent ---
(In reply to comment #8)
> (In reply to comment #7)
> > I tried some Firefoxes from 13.0 upwards. For me clearing caches and forcing
> > reload reliably solved the issue of pages not finishing.
>
> That should
https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
--- Comment #12 from Matthew Flaschen ---
This might need to be filed upstream.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
Wiki
https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
--- Comment #11 from Matthew Flaschen ---
(In reply to comment #10)
> I've been asked several times on IRC about this problem, and the above
> procedure always fixed the problem reliably. So to me, it's not a problem
> of the old or the new ger
https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
--- Comment #10 from christ...@quelltextlich.at ---
Seeing the priority got bumped to High ... I'd rather close this bug.
The problem stems from upgrading gerrit.
People are simply having documents from the old gerrit in the browser cache.
Typ
https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
Andre Klapper changed:
What|Removed |Added
Priority|Unprioritized |High
--
You are receiving this mail b
https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
--- Comment #9 from christ...@quelltextlich.at ---
We just had a report that logging out and in again was required twice on
Firefox 20. Then it worked again.
(When logged out, the change loaded without any problem)
--
You are receiving this m
https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
--- Comment #8 from christ...@quelltextlich.at ---
(In reply to comment #7)
> I tried some Firefoxes from 13.0 upwards. For me clearing caches and forcing
> reload reliably solved the issue of pages not finishing.
That should have been:
* Loggi
https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
--- Comment #7 from christ...@quelltextlich.at ---
I tried some Firefoxes from 13.0 upwards. For me clearing caches and forcing
reload reliably solved the issue of pages not finishing.
(In reply to comment #5)
> I'm getting this issue again des
https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
Matthew Flaschen changed:
What|Removed |Added
CC||mflasc...@wikimedia.org
--- Comment
https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
--- Comment #5 from Gabriel Wicke ---
I'm getting this issue again despite upgrading to 22. I only happens on a
particular patch page. Error in JS console:
[13:10:00.110] Thu Jun 27 13:10:00 GMT-700 2013 Class$3
SEVERE: (TypeError)
stack:
Ex
https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
--- Comment #4 from Roan Kattouw ---
(In reply to comment #3)
> Subbu experiences similar issues with FF 22. Maybe a cache / localstorage
> issue
> after all?
Looks like it might be that. I just opened a private window and logged into
Gerrit th
https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
--- Comment #3 from Gabriel Wicke ---
Subbu experiences similar issues with FF 22. Maybe a cache / localstorage issue
after all?
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
Roan Kattouw changed:
What|Removed |Added
CC||roan.katt...@gmail.com
--- Comment #2 f
https://bugzilla.wikimedia.org/show_bug.cgi?id=50309
--- Comment #1 from Gabriel Wicke ---
After upgrading to Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101
Firefox/22.0 Iceweasel/22.0 which just hit Debian experimental the issue is
gone. Chad indicated that it works for him using either
24 matches
Mail list logo
