Error is thrown when trying to run the connector
See original GitHub issueI started seeing some weird errors. The following is (truncated) exec logs.
START:
05 11 2020 10:43:50.784:WARN [filelist]: Pattern "/home/pawel/workspace/arc/amf-helper-mixin/__snapshots__/**/*.md" does not match any file.
05 11 2020 10:43:50.804:INFO [karma-server]: Karma v5.2.3 server started at http://localhost:9878/
05 11 2020 10:43:50.804:INFO [launcher]: Launching browsers ChromeHeadlessNoSandbox, SL_Chrome, SL_Chrome-1, SL_Firefox, SL_Firefox-1, SL_Safari, SL_Safari-1, SL_EDGE, SL_EDGE-1 with concurrency unlimited
05 11 2020 10:43:50.808:INFO [launcher]: Starting browser ChromeHeadless
05 11 2020 10:43:50.815:INFO [launcher]: Starting browser chrome latest Windows 10 on SauceLabs
05 11 2020 10:43:50.830:INFO [launcher]: Starting browser chrome latest-1 Windows 10 on SauceLabs
05 11 2020 10:43:50.831:INFO [launcher]: Starting browser firefox latest Windows 10 on SauceLabs
05 11 2020 10:43:50.838:INFO [launcher]: Starting browser firefox latest-1 Windows 10 on SauceLabs
05 11 2020 10:43:50.838:INFO [launcher]: Starting browser safari latest macOS 10.13 on SauceLabs
05 11 2020 10:43:50.838:INFO [launcher]: Starting browser safari latest-1 macOS 10.13 on SauceLabs
05 11 2020 10:43:50.838:INFO [launcher]: Starting browser microsoftedge latest Windows 10 on SauceLabs
05 11 2020 10:43:50.838:INFO [launcher]: Starting browser microsoftedge latest-1 Windows 10 on SauceLabs
05 11 2020 10:43:51.103:INFO [Chrome Headless 88.0.4300.0 (Linux x86_64)]: Connected on socket uQhvTH11QESdF977AAAA with id 42952097
05 11 2020 10:57:05.796:ERROR [karma-server]: UncaughtException:: Cannot read property 'results' of undefined
05 11 2020 10:57:05.798:ERROR [SaucelabsLauncher]: Could not quit the Saucelabs selenium connection. Failure message:
05 11 2020 10:57:05.799:ERROR [SaucelabsLauncher]: TypeError: Cannot read property 'deleteSession' of null
at SaucelabsLauncher.<anonymous> (/home/pawel/workspace/arc/amf-helper-mixin/node_modules/karma-sauce-launcher/dist/launcher/launcher.js:139:26)
at Generator.next (<anonymous>:null:null)
at /home/pawel/workspace/arc/amf-helper-mixin/node_modules/karma-sauce-launcher/dist/launcher/launcher.js:8:71
at new Promise (<anonymous>:null:null)
at __awaiter (/home/pawel/workspace/arc/amf-helper-mixin/node_modules/karma-sauce-launcher/dist/launcher/launcher.js:4:12)
at SaucelabsLauncher.<anonymous> (/home/pawel/workspace/arc/amf-helper-mixin/node_modules/karma-sauce-launcher/dist/launcher/launcher.js:131:31)
at SaucelabsLauncher.emit (events.js:315:20)
at SaucelabsLauncher.EventEmitter.emit (domain.js:486:12)
at SaucelabsLauncher.emitAsync (/home/pawel/workspace/arc/amf-helper-mixin/node_modules/karma/lib/events.js:52:10)
at SaucelabsLauncher.BaseLauncher.kill (/home/pawel/workspace/arc/amf-helper-mixin/node_modules/karma/lib/launchers/base.js:61:27)
at SaucelabsLauncher.BaseLauncher.forceKill (/home/pawel/workspace/arc/amf-helper-mixin/node_modules/karma/lib/launchers/base.js:71:10)
at /home/pawel/workspace/arc/amf-helper-mixin/node_modules/karma/lib/launcher.js:172:35
at Array.map (<anonymous>:null:null)
at Launcher.killAll (/home/pawel/workspace/arc/amf-helper-mixin/node_modules/karma/lib/launcher.js:172:10)
at Server.<anonymous> (/home/pawel/workspace/arc/amf-helper-mixin/node_modules/karma/lib/launcher.js:51:49)
at Server.emit (events.js:327:22)
at Server.EventEmitter.emit (domain.js:486:12)
at Server.emitExitAsync (/home/pawel/workspace/arc/amf-helper-mixin/node_modules/karma/lib/server.js:155:12)
at disconnectBrowsers (/home/pawel/workspace/arc/amf-helper-mixin/node_modules/karma/lib/server.js:387:12)
at reportError (/home/pawel/workspace/arc/amf-helper-mixin/node_modules/karma/lib/server.js:419:7)
at process.<anonymous> (/home/pawel/workspace/arc/amf-helper-mixin/node_modules/karma/lib/server.js:430:7)
at process.emit (events.js:327:22)
at process.EventEmitter.emit (domain.js:486:12)
at process._fatalException (internal/process/execution.js:156:25)
05 11 2020 10:57:05.801:ERROR [karma-server]: TypeError: Cannot read property 'results' of undefined
at SaucelabsReporter.onSpecComplete (/home/pawel/workspace/arc/amf-helper-mixin/node_modules/karma-sauce-launcher/dist/reporter/reporter.js:29:35)
at Server.<anonymous> (/home/pawel/workspace/arc/amf-helper-mixin/node_modules/karma/lib/events.js:40:26)
at Server.emit (events.js:327:22)
at Server.EventEmitter.emit (domain.js:486:12)
at Browser.onResult (/home/pawel/workspace/arc/amf-helper-mixin/node_modules/karma/lib/browser.js:159:20)
at Socket.<anonymous> (/home/pawel/workspace/arc/amf-helper-mixin/node_modules/karma/lib/browser.js:209:42)
at Socket.emit (events.js:315:20)
at /home/pawel/workspace/arc/amf-helper-mixin/node_modules/socket.io/lib/socket.js:528:12
at processTicksAndRejections (internal/process/task_queues.js:75:11)
TypeError: Cannot read property 'results' of undefined
at SaucelabsReporter.onSpecComplete (/home/pawel/workspace/arc/amf-helper-mixin/node_modules/karma-sauce-launcher/dist/reporter/reporter.js:29:35)
at Server.<anonymous> (/home/pawel/workspace/arc/amf-helper-mixin/node_modules/karma/lib/events.js:40:26)
at Server.emit (events.js:327:22)
at Server.EventEmitter.emit (domain.js:486:12)
at Browser.onResult (/home/pawel/workspace/arc/amf-helper-mixin/node_modules/karma/lib/browser.js:159:20)
at Socket.<anonymous> (/home/pawel/workspace/arc/amf-helper-mixin/node_modules/karma/lib/browser.js:209:42)
at Socket.emit (events.js:315:20)
at /home/pawel/workspace/arc/amf-helper-mixin/node_modules/socket.io/lib/socket.js:528:12
at processTicksAndRejections (internal/process/task_queues.js:75:11)
I am not sure where exactly the problem is. I was trying to change the configuration to bare minimum, then i tried to copy the configuration from the readme file but still no luck. Regular karma tests are executed locally and on Travis. The errors start only when trying to run SL tests. I am hoping for a help with solving this.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:12
Top Results From Across the Web
Database connector is not throwing exception
Hi, I have a database connector in flow calling stored procedure in MS Server. Stored procedure throws exception in some cases when validation ......
Read more >Developing connectors - Connector exception handling - IBM
The IBridge interface defines exceptions that each method in a connector might return. The exception thrown should reflect the condition that occurred.
Read more >Error handling and messages for Community Connectors
Showing error details based on admin status; Throwing user facing errors. Best practices for handling connector errors.
Read more >Exception in getting authentication header When Trying to ...
Identity Manager Connector - Version 12.2.1.3.0 and later: Office365 Connector Throwing Error : ConnectorException: Exception in getting ...
Read more >Throwing an error in Catch loses connector documents
My first guess is that the issue has something to do with where the Try/Catch is in relation to the Connector. I think...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@TwoPlusTwoOne could you please reproduce this in a separate repo? Please, create a new repo in our org with this issue.
I don’t have write access to the repo so would have to open another PR but the cycle time between trying a change, opening a PR, merging to master is pretty gnarly 😅 I thought I could fix it by just bumping the version but that didn’t work out. Maybe the maintainers might be up for it but ya unfortunately PRs don’t run with Sauce creds until merged.
It was literally just bugging me all the build indicators were red haha
https://github.com/axios/axios#browser-support