Error: socket.io connection error: {"type":"TransportError","description":0}
See original GitHub issueIntroduction of a2554fff2204586c61c9bc33f638ccdf562e0eb8 made a problem in the tests appear.
https://travis-ci.org/github/ether/etherpad-lite/jobs/737680722#L3586
[2020-10-21 10:58:18.145] [WARN] client - Error: socket.io connection error: {"type":"TransportError","description":0} -- { errorId: 'y5bvv2vRcJP3P2OhF2M3', msg: 'Error: socket.io connection error: {"type":"TransportError","description":0}', url: 'http://localhost:9001/p/FRONTEND_TEST_whfdzDgZSWTDON78O2hH', source: 'http://localhost:9001/javascripts/lib/ep_[secure]/static/js/pad.js?callback=require.define&v=89e63f2c', linenumber: 225, userAgent: 'Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0' }
This seems to happen only on Windows and Firefox before navigating to the timeslider with:
var iframe = $('#iframe-container iframe'); iframe.attr('src', iframe.attr('src')+'/timeslider' + revision);
I am not sure if the error goes away, if we go to the timeslider via button, if it’s related to https://github.com/socketio/engine.io/pull/601/files because we are closing the socket.io connection or if we have a bug in our code.
It does not seem to have an impact on the reliability of the tests.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (5 by maintainers)
The socket.io errors in the test runs are benign. They have always been there, we just didn’t see them until #4420 was merged. I’ll see what I can do to eliminate the noise.
Please follow the issue guidelines.