Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TypeError: Cannot set property '5841760' of null at initliazeXmlForBrowser #28

Open
AryanJ-NYC opened this issue Jul 26, 2018 · 5 comments
Assignees
Labels

Comments

@AryanJ-NYC
Copy link

AryanJ-NYC commented Jul 26, 2018

TypeError: Cannot set property '56021360' of null
    at initliazeXmlForBrowser (karma-sonarqube-unit-reporter/index.js:50:40)
    at SonarQubeUnitReporter.onBrowserStart (karma-sonarqube-unit-reporter/index.js:106:5)
    at Server.<anonymous> (karma/lib/events.js:40:26)
    at Server.emit (events.js:187:15)
    at Browser.onStart (karma/lib/browser.js:123:18)
    at Socket.socket.on (karma/lib/browser.js:269:39)
    at Socket.emit (events.js:182:13)
    at socket.io/lib/socket.js:513:12
    at process._tickCallback (internal/process/next_tick.js:61:11)
(node:58825) [DEP0079] DeprecationWarning: Custom inspection function on Objects via .inspect() is deprecated

Versions:

"jasmine-core": "~3.1.0",
"jasmine-spec-reporter": "~4.2.1",
"karma": "~2.0.5",
"karma-coverage-istanbul-reporter": "^2.0.1",
"karma-jasmine": "~1.1.2",
"karma-jasmine-html-reporter": "^0.2.2",
"karma-phantomjs-launcher": "^1.0.4",
"karma-sonarqube-unit-reporter": "0.0.17",

Bug reproduced when saving a spec file while tests are running.

Similar junit bugs:
karma-runner/karma-junit-reporter#20
karma-runner/karma-junit-reporter#61

@llehn
Copy link

llehn commented Aug 31, 2018

We have same problem. Weird thing is, it used to work, and this error started showing up without any relevant package.json changes

@tornaia tornaia added the bug label Sep 5, 2018
@tornaia tornaia self-assigned this Sep 5, 2018
@llehn
Copy link

llehn commented Sep 7, 2018

We changed tests to run in Chrome instead of ChromeHeadless and the issue vanished.

@Manish2005
Copy link

Just wondering if there's any update on this issue?

@SanthoshBanavath
Copy link

Is there any fix or update on this?

@andreas-mueller-2504
Copy link

As a workaround it helped to downgrade socket.io to 4.7.0.

{
...
    "overrides": {
        "socket.io": "4.7.0"
    }
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants