Open
Bug 1447462
Opened 8 years ago
Updated 8 years ago
fxheads is intermittently available
Categories
(Developer Services :: Mercurial: hg.mozilla.org, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: alice0775, Unassigned)
References
()
Details
Attachments
(2 files)
I do not know this is a server problem or Firefox problem.
I noticed when testing Bug 1447193.
Sometimes the content of the page is different when opening the same page on multiple tabs. see attached.
| Reporter | ||
Comment 1•8 years ago
|
||
| Reporter | ||
Updated•8 years ago
|
status-firefox61:
affected → ---
Component: General → Mercurial: hg.mozilla.org
Product: Core → Developer Services
| Reporter | ||
Comment 2•8 years ago
|
||
reproduced on 58-61.0a1.
so, it seems server(cdn?) data is not syncing properly.
Summary: Sometimes the content of the page is different when opening the same page on multiple tabs. → https://hg.mozilla.org server(cdn?) data is not syncing properly
odd.. hitting a single webhead directly (eg. http://hgweb14.dmz.scl3.mozilla.com/mozilla-central/help ) and refreshing still triggers the issue.
http://hgweb14.dmz.scl3.mozilla.com/mozilla-central/help/fxheads will occasionally trigger an ise. but that's just "Abort: no such help topic: fxheads".
fxheads comes from the firefoxtree extension. i'm more confused by it sometimes being present rather than it sometimes being absent.
Comment 5•8 years ago
|
||
glob did you find a root cause for this bug? Do you want to take ownership of this bug? (I'm just triaging our bucket)
Flags: needinfo?(glob)
Updated•8 years ago
|
Summary: https://hg.mozilla.org server(cdn?) data is not syncing properly → fxheads is intermittently available
(In reply to Kim Moir [:kmoir] ET from comment #5)
> glob did you find a root cause for this bug?
no, sorry. t'was just some drive-by diagnostics while waiting for other tasks to complete.
iirc fxheads wasn't configured anywhere i looked.
> Do you want to take ownership of this bug?
it's probably better handled by connor or gps.
Flags: needinfo?(glob)
You need to log in
before you can comment on or make changes to this bug.
Description
•