WardCunningham
Unexpected Network Changed Error
Occassionally changes will fail to post, giving orange halo. Most confusingly, this happens in situations where there is no load, persona login is maintained, and the page/edit is not particularly large. Repeatedly trying to fork the page sometimes works as solution, but often it takes multiple times.
I caught one of these today while my browser log was open. It appears as a "networked changed" error. See screenshot.
It seems you have caught something "red handed". Now if we can just figure out what?
As I browse for mentions of this error I get the feeling that it is caused by shifting network paths possibly caused by ip4/ip6, cat5/wifi, or vpn/direct alternatives. Any chance any of these could be in play?
When I get an unexpected fork-to-local I have cleared error conditions by reloading the web page. This is a no-risk option with my changes safely stored. When I've had server load based errors a retry without reload also worked.
The journal entry for an unexpected fork-to-local will include the error message reported by the failed ajax call. This can be viewed by double-clicking the timestamp on the revision page. I've yet to see the browser offer a better description via ajax than appears in the inspector window.
Wow. What a great reminder that there are many layers beneath us. I wonder if WSUV networking folks could shed some light on Mike's particular situation?
Actually, at this point I was on T-Mobile 3g. I'll see if I can collect errors on ethernet and wifi connections as well.
Also, weirdly the error caught in journal looks like this:
{ "type": "edit", "id": "fa75743835d1a9ac", "item": { "type": "paragraph", "id": "fa75743835d1a9ac", "text": "[[Importing Course Items]]" }, "date": 1413330027435, "error": { "type": "error", "msg": "" } }
Which browser are you using? The screen shot looks like Chrome.
As much as I hate to suggest it, have you tried a different browser? As all the reports seem to indicate that this problem is only seen with Chrome.