Missing error handler on `socket`. #1751

binarykitchen · 2015-12-07T22:54:56Z

I am seeing this in the current test set up and would like to catch this kind of error from the karma server instance. Is that possible?

csmalin · 2015-12-18T17:12:39Z

I'm only seeing this problem when using karma-jenkins-reporter or karma-junit-reporter, are you using any of these plugins?

binarykitchen · 2015-12-20T20:51:48Z

no

priley86 · 2015-12-21T02:09:40Z

+1 seeing this with karma-junit-reporter in my tests with Node 4.23 LTS...any ideas?

    "karma": "~0.13.15",
    "karma-chrome-launcher": "~0.2.0",
    "karma-coverage": "~0.4.2",
    "karma-firefox-launcher": "~0.1.6",
    "karma-jasmine": "~0.3.6",
    "karma-junit-reporter": "^0.2.2",
    "karma-ng-html2js-preprocessor": "^0.1.2",
    "karma-phantomjs-launcher": "~0.2.0",
    "socket.io": "^1.3.7",

PhantomJS 1.9.8 (Mac OS X 0.0.0): Executed 48 of 277 (26 FAILED) ERROR (0.732 secs / 0.769 secs)
Missing error handler on socket.
TypeError: Cannot read property '68890579' of null
at specSuccess.specSkipped.specFailure (/Users/patrick/Projects/community/node_modules/karma-junit-reporter/index.js:89:22)
at onSpecComplete (/Users/patrick/Projects/community/node_modules/karma/lib/reporters/base.js:78:12)
at null. (/Users/patrick/Projects/community/node_modules/karma/lib/events.js:13:22)
at emitTwo (events.js:92:20)
at emit (events.js:172:7)
at onResult (/Users/patrick/Projects/community/node_modules/karma/lib/browser.js:216:13)
at Socket. (/Users/patrick/Projects/community/node_modules/karma/lib/events.js:13:22)
at emitOne (events.js:82:20)
at Socket.emit (events.js:169:7)
at Socket.onevent (/Users/patrick/Projects/community/node_modules/socket.io/lib/socket.js:330:8)
at Socket.onpacket (/Users/patrick/Projects/community/node_modules/socket.io/lib/socket.js:290:12)
at Client.ondecoded (/Users/patrick/Projects/community/node_modules/socket.io/lib/client.js:193:14)
at Decoder.Emitter.emit (/Users/patrick/Projects/community/node_modules/socket.io/node_modules/socket.io-parser/node_modules/component-emitter/index.js:134:20)
at Decoder.add (/Users/patrick/Projects/community/node_modules/socket.io/node_modules/socket.io-parser/index.js:247:12)
at Client.ondata (/Users/patrick/Projects/community/node_modules/socket.io/lib/client.js:175:18)
at emitOne (events.js:77:13)
at Socket.emit (events.js:169:7)
at Socket.onPacket (/Users/patrick/Projects/community/node_modules/socket.io/node_modules/engine.io/lib/socket.js:99:14)
at emitOne (events.js:82:20)
at WebSocket.emit (events.js:169:7)
at WebSocket.Transport.onPacket (/Users/patrick/Projects/community/node_modules/socket.io/node_modules/engine.io/lib/transport.js:91:8)
at WebSocket.Transport.onData (/Users/patrick/Projects/community/node_modules/socket.io/node_modules/engine.io/lib/transport.js:102:8)

wentaohong · 2015-12-28T20:42:02Z

Same error here: any suggestions?
PhantomJS 1.9.8 (Mac OS X 0.0.0): Executed 32 of 141 ERROR (0.428 secs / 0.427 secs)
Missing error handler on socket.
TypeError: Cannot read property '12945726' of null

levithomason · 2016-01-06T01:14:27Z

Getting with PhantomJS and the spec reporter. Trying to figure out why it is only on CircleCI and not locally:

Missing error handler on `socket`.
TypeError: sockets.forEach is not a function
    at disconnectBrowsers (/home/ubuntu/[app]/node_modules/karma/lib/server.js:314:13)
    at [object Object].<anonymous> (/home/ubuntu/[app]/node_modules/karma/lib/server.js:291:7)
    at emitTwo (events.js:92:20)
    at [object Object].emit (events.js:172:7)
    at emitRunCompleteIfAllBrowsersDone (/home/ubuntu/[app]/node_modules/karma/lib/server.js:256:12)
    at [object Object].<anonymous> (/home/ubuntu/[app]/node_modules/karma/lib/server.js:278:9)
    at emitTwo (events.js:92:20)
    at [object Object].emit (events.js:172:7)
    at [object Object].onComplete (/home/ubuntu/[app]/node_modules/karma/lib/browser.js:142:13)
    at Socket.<anonymous> (/home/ubuntu/[app]/node_modules/karma/lib/events.js:13:22)
    at emitTwo (events.js:92:20)
    at Socket.emit (events.js:172:7)
    at Socket.onevent (/home/ubuntu/[app]/node_modules/socket.io/lib/socket.js:335:8)
    at Socket.onpacket (/home/ubuntu/[app]/node_modules/socket.io/lib/socket.js:295:12)
    at Client.ondecoded (/home/ubuntu/[app]/node_modules/socket.io/lib/client.js:193:14)
    at Decoder.Emitter.emit (/home/ubuntu/[app]/node_modules/component-emitter/index.js:134:20)
    at Decoder.add (/home/ubuntu/[app]/node_modules/socket.io-parser/index.js:247:12)
    at Client.ondata (/home/ubuntu/[app]/node_modules/socket.io/lib/client.js:175:18)
    at emitOne (events.js:77:13)
    at Socket.emit (events.js:169:7)
    at Socket.onPacket (/home/ubuntu/[app]/node_modules/engine.io/lib/socket.js:101:14)
    at emitOne (events.js:77:13)

levithomason · 2016-01-06T01:39:24Z

Our issue was just fixed in 3ab78d6 and shipped in 0.13.19. Thanks!

Fixes #1782

damassi · 2016-01-06T05:07:56Z

Confirmed fixed.

see https://github.com/karma-runner/karma/blob/master/CHANGELOG.md#01319-2016-01-06 and karma-runner/karma#1751

adam-beck · 2016-03-11T22:12:45Z

I'm still seeing this in 0.13.22

dignifiedquire · 2016-03-13T19:42:05Z

@adam-beck please provide a reproducible example.

sharikovvladislav · 2016-04-04T07:23:40Z

@dignifiedquire what example do you want? I have same issue using karma: 0.13.22 and karma-teamcity-reporter: 0.2.2.

[10:09:26]  Missing error handler on `socket`.
[10:09:26]  Error: EAGAIN: resource temporarily unavailable, write
[10:09:26]      at Error (native)
[10:09:26]      at Function.fs.writeSync (fs.js:669:18)
[10:09:26]      at /export/home/bc_prod1/buildAgent/work/dac7c6b3e0abf1a1/node_modules/karma/lib/reporters/base.js:51:7
[10:09:26]      at Array.forEach (native)
[10:09:26]      at write (/export/home/bc_prod1/buildAgent/work/dac7c6b3e0abf1a1/node_modules/karma/lib/reporters/base.js:50:19)
[10:09:26]      at onBrowserLog (/export/home/bc_prod1/buildAgent/work/dac7c6b3e0abf1a1/node_modules/karma/lib/reporters/base.js:70:12)
[10:09:26]      at null.<anonymous> (/export/home/bc_prod1/buildAgent/work/dac7c6b3e0abf1a1/node_modules/karma/lib/events.js:13:22)
[10:09:26]      at emitThree (events.js:102:20)
[10:09:26]      at emit (events.js:175:7)
[10:09:26]      at onInfo (/export/home/bc_prod1/buildAgent/work/dac7c6b3e0abf1a1/node_modules/karma/lib/browser.js:111:15)
[10:09:26]      at Socket.<anonymous> (/export/home/bc_prod1/buildAgent/work/dac7c6b3e0abf1a1/node_modules/karma/lib/events.js:13:22)
[10:09:26]      at emitOne (events.js:82:20)
[10:09:26]      at Socket.emit (events.js:169:7)
[10:09:26]      at Socket.onevent (/export/home/bc_prod1/buildAgent/work/dac7c6b3e0abf1a1/node_modules/socket.io/lib/socket.js:335:8)
[10:09:26]      at Socket.onpacket (/export/home/bc_prod1/buildAgent/work/dac7c6b3e0abf1a1/node_modules/socket.io/lib/socket.js:295:12)
[10:09:26]      at Client.ondecoded (/export/home/bc_prod1/buildAgent/work/dac7c6b3e0abf1a1/node_modules/socket.io/lib/client.js:193:14)

Note, that I am getting this issue only in TeamCity environment. Karma runner works on Redhat 6. I can provide more info, if you need.

Same run on Windows 7 with same teamcity reporter works perfectly.

One of the differences: on teamcity all node packages in node_modules were installed in linux environment.

Looks like I got this error only on tests which are using httpBackend service. So I got this issue when some async factor influence test run.

Example of test:

it("livescrolling test", function () {
  // mock
  scope.a.b.c = {
    foo: noopFn
  };
  $httpBackend.expectGET(/(.*?)a\/b\/c(.*?)/).respond({
    a: [{a: 5, b: "someDate"}],
    m: {
      x: 10,
      y: 20,
      z: 0
    }
  });
  // prepare
  spyOn(scope.d.e.f, 'foo');
  scope.m.n.o = [{a: 5, b: "someDate"}];
  expect(scope.a.b.c).toEqual(1);
  expect(scope.m.n.o).toEqual(10);
  ctrl.someFoo(123, 456, true);
  $httpBackend.flush();
  expect(scope.a.b.c).toHaveBeenCalledWith({a: false});
});

fs throws error. Looks like some messages were pushed to somewhere (stdout) and fs thrown error about it is not available. May be it is because I don't use httpBackend correctly?

fwielstra · 2016-04-05T08:18:56Z

I've just run into this issue (via karma-junit-reporter); in our case the problem seemed to be a dependency that was mangled by a (company wifi) proxy / firewall / filter. Running npm install via a tethered smartphone resolved the issue. NPM needs signature verification.

scaljeri · 2016-04-10T15:56:41Z

+1 I'm getting the same error. To reproduce you can checkout my project here.

$> npm install
$> gulp test

Maybe you have to run gulp twice before you see this error.

vlki · 2016-05-07T00:17:47Z

Seeing same error as @sharikovvladislav when using karma and karma-teamcity-reporter together.

Missing error handler on `socket`.
Error: EAGAIN: resource temporarily unavailable, write

Tried other reporters like progress and dots, no error there
Error started showing after update from node 5.11.0 to 6.1.0; checked 5.11.0, 6.0.0, 6.1.0, and error is on 6.0.0 and 6.1.0 (Mac OS X 10.11.4), no error on 5.11.0

Minimal setup with which I am able to reproduce the error here

shaikhspear16 · 2016-05-07T11:12:54Z

I get this error when i add 'browserify' to preprocessors.


 preprocessors: {
            'unit-test/linkers/**/!(*spec).js': ['coverage','browserify']
        }

I was getting require not found when running karma, that made me add browserify, now i get this error

neilkyoung · 2016-05-20T15:03:13Z

Confirm that I also get this error running MacOSX 10.11.1 (15B42):

Missing error handler onsocket. TypeError: (msg || "").replace is not a function

Karma version is 0.13.22.

shoesel · 2016-06-29T13:42:47Z

Seems this is back in Karma 1.1.0 (it was not occuring in 0.13.22)
I'm running tests with --single-run false in PhantomJS 2.1.1 on MacOSX 10.11.4
Output is:

PhantomJS 2.1.1 (Mac OS X 0.0.0): Executed 3281 of 3302 (skipped 21) SUCCESS (25.1 secs / 23.617 secs)
Missing error handler on 'socket'.
TypeError: Cannot read property '93062136' of null
  at onBrowserComplete (/PATH-TO/node_modules/karma-junit-reporter/index.js:120:23)
  at .<anonymous> (/PATH-TO/node_modules/karma/lib/events.js:13:22)
  at emitTwo (events.js:111:20)
  at emit (events.js:191:7)
  at onComplete (/PATH-TO/node_modules/karma/lib/browser.js:143:13)
  at Socket.<anonymous> (/PATH-TO/node_modules/karma/lib/events.js:13:22)
  at emitTwo (events.js:111:20)
  at Socket.emit (events.js:191:7)
  at Socket.onevent (/PATH-TO/node_modules/socket.io/lib/socket.js:335:8)
  at Socket.onpacket (/PATH-TO/node_modules/socket.io/lib/socket.js:295:12)
  at Client.ondecoded (/PATH-TO/node_modules/socket.io/lib/client.js:193:14)
  at Decoder.Emitter.emit (/PATH-TO/node_modules/component-emitter/index.js:134:20)
  at Decoder.add (/PATH-TO/node_modules/socket.io-parser/index.js:247:12)
  at Client.ondata (/PATH-TO/node_modules/socket.io/lib/client.js:175:18)
  at emitOne (events.js:96:13)
  at Socket.emit (events.js:188:7)
  at Socket.onPacket (/PATH-TO/node_modules/engine.io/lib/socket.js:101:14)
  at emitOne (events.js:96:13)
  at WebSocket.emit (events.js:188:7)
  at WebSocket.Transport.onPacket (/PATH-TO/node_modules/engine.io/lib/transport.js:104:8)
  at WebSocket.Transport.onData (/PATH-TO/node_modules/engine.io/lib/transport.js:115:8)
  at WebSocket.onData (/PATH-TO/node_modules/engine.io/lib/transports/websocket.js:76:30)
  at emitTwo (events.js:106:13)
  at WebSocket.emit (events.js:191:7)
  at Receiver.ontext (/PATH-TO/node_modules/ws/lib/WebSocket.js:816:10)
  at /PATH-TO/node_modules/ws/lib/Receiver.js:477:18
  at Receiver.applyExtensions (/PATH-TO/node_modules/ws/lib/Receiver.js:364:5)
  at /PATH-TO/node_modules/ws/lib/Receiver.js:466:14
  at Receiver.flush (/PATH-TO/node_modules/ws/lib/Receiver.js:340:3)
  at Receiver.opcodes.1.finish (/PATH-TO/node_modules/ws/lib/Receiver.js:482:12)
  at Receiver.expectHandler (/PATH-TO/node_modules/ws/lib/Receiver.js:451:33)
  at Receiver.add (/PATH-TO/node_modules/ws/lib/Receiver.js:95:24)
  at Socket.realHandler (/PATH-TO/node_modules/ws/lib/WebSocket.js:800:20)
  at emitOne (events.js:96:13)
  at Socket.emit (events.js:188:7)
  at readableAddChunk (_stream_readable.js:172:18)
  at Socket.Readable.push (_stream_readable.js:130:10)
  at TCP.onread (net.js:542:20)

PhantomJS 2.1.1 (Mac OS X 0.0.0) ERROR
  Disconnectedundefined

richburdon · 2016-06-30T20:15:28Z

+1

murrayju · 2016-07-14T15:34:39Z

+1, I see the same behavior as @shoesel

stramel · 2016-07-21T19:03:20Z

+1, Having the issue as well

HipsterZipster · 2016-07-22T06:10:20Z

+1 having issue on karma 1.1.1 without karma-junit-reporter

dignifiedquire · 2016-07-26T07:05:29Z

I haven't been able to reproduce this issue, so I need a repo that I can clone and run that shows this issue.

…ML URL encoded characters. Karma fails on Jenkins when it checks out branches containing '/' as it converts it to '%2F'. Fixes errors seen on karma-runner#1751, karma-runner#61.

narainsagar · 2016-08-30T14:11:00Z

I am also getting the same error with angular-cli project, I am using these versions:

"angular-cli": "^1.0.0-beta.10",
"karma": "0.13.22",
"karma-phantomjs-launcher": "^1.0.0",
"karma-jasmine": "0.3.8",

If anyone want to check - may clone this repo. Thanks.

MadaraUchiha · 2016-09-05T09:45:47Z

Can this please be reopened? I'm getting the same error here.

Svjard · 2016-09-07T18:21:07Z

Getting this same issue. Very basic configuration with angular cli.

santiagoGuti · 2016-09-12T15:45:32Z

getting the same issue

    "karma": "0.13.22",
    "karma-chrome-launcher": "0.2.3",
    "karma-cli": "0.1.2",
    "karma-jasmine": "0.3.8",
    "karma-junit-reporter": "0.4.1",
    "karma-notify-reporter": "0.1.1"

colllin · 2016-09-14T16:54:24Z

The problem for me was using Node v6 with karma-jenkins-reporter, which is apparently deprecated. The solution was to switch to karma-junit-reporter.

marinho · 2016-09-16T07:29:52Z

It happens for me with karma-junit-reporter@1.1.0 and karma@1.3.0, but only when I have this plugin on my webpack config:

new WebpackShellPlugin({
  onBuildStart: [ 'npm run generate-spec-with-all' ]
}),

The mentioned script just globs a folder, parses some file and generate a dumb spec file with only require calls. It runs fast and works if I call it as npm run generate-spec-with-all && before the test runner.

Update: and it happens only when calling with --auto-watch and --no-single-run.

fbobbio · 2016-09-28T15:30:34Z

+1 with karma 1.3.0 and karma-junit-reporter 1.1.0 on Ubuntu 16_04

orestes · 2016-10-02T22:14:11Z

Same problem here karma-junit-reporter 1.1.0, karma 1.3.0. Any leads?

stramel · 2016-10-03T01:29:54Z

I am only running into issues with Windows 8 now.

noherczeg · 2016-10-13T22:03:54Z

Upgrading PhantomJS and leaving grunt-karma out of the game fixed this for me. It seems to me that grunt-karma is causing the issue.

ibbatta · 2016-11-23T09:37:21Z

+1 for me

karma 1.3.0

randakar · 2016-12-02T14:01:54Z

+1

nadhir-falta · 2016-12-12T22:44:44Z

Same problem here karma-junit-reporter 1.1.0, karma 1.3.0, any news about this?

randakar · 2016-12-13T07:01:14Z

karma-junit-reporter 1.2.0 should make this error message go away. Though it's quite likely other reporter suffer from the same (or at least something very similar) issue. I'm pretty sure the Jenkins one does.

levithomason referenced this issue Jan 6, 2016

fix(server): Handle new socket.io internal format.

3ab78d6

Fixes #1782

dignifiedquire closed this as completed Jan 6, 2016

bdefore added a commit to bdefore/universal-redux that referenced this issue Jan 8, 2016

update karma due to karma-runner/karma#1751

654f9fc

krasimir mentioned this issue Jan 20, 2016

Some errors on npm test krasimir/react-webpack-starter#6

Closed

benvinegar added a commit to getsentry/sentry that referenced this issue Jan 26, 2016

Bump karma to 0.13.19 to address karma-runner/karma#1751

1b33e50

lukfugl added a commit to lukfugl/rackt-cli that referenced this issue Jan 29, 2016

bump karma version for socket.io bug

49683e8

see https://github.com/karma-runner/karma/blob/master/CHANGELOG.md#01319-2016-01-06 and karma-runner/karma#1751

lukfugl mentioned this issue Jan 29, 2016

bump karma version for socket.io bug mzabriskie/rackt-cli#23

Merged

georgeedwards mentioned this issue Apr 5, 2016

Missing error handler on socket #2042

Open

shoesel mentioned this issue Jun 30, 2016

Cannot read property '33038646' of null - karma-junit-reporter/index.js:93:22 karma-runner/karma-junit-reporter#61

Closed

dam-ien mentioned this issue Aug 3, 2016

fix(web-server): Allow karma to run in project which path contains HTML URL encoded characters #2297

Merged

mdocter mentioned this issue Sep 13, 2016

TypeError: (msg || "").replace is not a function #2168

Closed

Omrisnyk mentioned this issue Oct 27, 2023

[Snyk] Fix for 2 vulnerabilities Omrisnyk/npm-lockfiles#122

Open

Omrisnyk mentioned this issue Dec 15, 2023

[Snyk] Security upgrade karma from 2.0.3 to 3.0.0 Omrisnyk/npm-lockfiles#132

Open

Missing error handler on socket. #1751

Missing error handler on socket. #1751

Comments

binarykitchen commented Dec 7, 2015

csmalin commented Dec 18, 2015

binarykitchen commented Dec 20, 2015

priley86 commented Dec 21, 2015

wentaohong commented Dec 28, 2015

levithomason commented Jan 6, 2016

levithomason commented Jan 6, 2016

damassi commented Jan 6, 2016

adam-beck commented Mar 11, 2016

dignifiedquire commented Mar 13, 2016

sharikovvladislav commented Apr 4, 2016

fwielstra commented Apr 5, 2016

scaljeri commented Apr 10, 2016

vlki commented May 7, 2016 • edited

shaikhspear16 commented May 7, 2016

neilkyoung commented May 20, 2016 • edited

shoesel commented Jun 29, 2016

richburdon commented Jun 30, 2016

murrayju commented Jul 14, 2016

stramel commented Jul 21, 2016

HipsterZipster commented Jul 22, 2016 • edited

dignifiedquire commented Jul 26, 2016

narainsagar commented Aug 30, 2016 • edited

MadaraUchiha commented Sep 5, 2016

Svjard commented Sep 7, 2016

santiagoGuti commented Sep 12, 2016 • edited

colllin commented Sep 14, 2016

marinho commented Sep 16, 2016 • edited

fbobbio commented Sep 28, 2016

orestes commented Oct 2, 2016

stramel commented Oct 3, 2016

noherczeg commented Oct 13, 2016 • edited

ibbatta commented Nov 23, 2016

randakar commented Dec 2, 2016

nadhir-falta commented Dec 12, 2016

randakar commented Dec 13, 2016

Missing error handler on `socket`. #1751

Missing error handler on `socket`. #1751

vlki commented May 7, 2016 •

edited

neilkyoung commented May 20, 2016 •

edited

HipsterZipster commented Jul 22, 2016 •

edited

narainsagar commented Aug 30, 2016 •

edited

santiagoGuti commented Sep 12, 2016 •

edited

marinho commented Sep 16, 2016 •

edited

noherczeg commented Oct 13, 2016 •

edited