Closed dzsodzso63 closed 4 years ago
Thanks for providing the details.
The only place I can see the test has run, is the Wallaby.js Console output
With the message like above in Wallaby Console, the issue is likely happens in the editor.
Can you please:
Developer: Toggle Developer Tools
command in VS Code),@ArtemGovorov Thx for the tip!
Here's the result (2 errors in the console):
1.
mainThreadExtensionService.ts:65 [[object Object]]Cannot read property 'document' of undefined
$onExtensionRuntimeError @ mainThreadExtensionService.ts:65
_doInvokeHandler @ rpcProtocol.ts:402
_invokeHandler @ rpcProtocol.ts:387
_receiveRequest @ rpcProtocol.ts:303
_receiveOneMessage @ rpcProtocol.ts:230
(anonymous) @ rpcProtocol.ts:105
fire @ event.ts:587
fire @ ipc.net.ts:453
_receiveMessage @ ipc.net.ts:733
(anonymous) @ ipc.net.ts:592
fire @ event.ts:587
acceptChunk @ ipc.net.ts:239
(anonymous) @ ipc.net.ts:200
t @ ipc.net.ts:28
emit @ events.js:203
addChunk @ _stream_readable.js:295
readableAddChunk @ _stream_readable.js:276
Readable.push @ _stream_readable.js:210
onStreamRead @ internal/stream_base_commons.js:166
2.
mainThreadExtensionService.ts:66 TypeError: Cannot read property 'document' of undefined
at d._isTimelineViewer (/Users/dzso/.vscode/extensions/wallabyjs.wallaby-vscode-1.0.213/dist/index.js:15)
at d.<anonymous> (/Users/dzso/.vscode/extensions/wallabyjs.wallaby-vscode-1.0.213/dist/index.js:15)
at d.emit (events.js:203)
at u.<anonymous> (/Users/dzso/.vscode/extensions/wallabyjs.wallaby-vscode-1.0.213/dist/index.js:15)
at u.emit (events.js:203)
at u._documentUpdates (/Users/dzso/.vscode/extensions/wallabyjs.wallaby-vscode-1.0.213/wallaby/client.js:14)
at WebSocket.<anonymous> (/Users/dzso/.vscode/extensions/wallabyjs.wallaby-vscode-1.0.213/wallaby/client.js:14)
at WebSocket.emit (events.js:203)
at Receiver.ontext (/Users/dzso/.vscode/extensions/wallabyjs.wallaby-vscode-1.0.213/wallaby/node_modules/ws/lib/WebSocket.js:841)
at /Users/dzso/.vscode/extensions/wallabyjs.wallaby-vscode-1.0.213/wallaby/node_modules/ws/lib/Receiver.js:536
at /Users/dzso/.vscode/extensions/wallabyjs.wallaby-vscode-1.0.213/wallaby/node_modules/ws/lib/Receiver.js:368
at /Users/dzso/.vscode/extensions/wallabyjs.wallaby-vscode-1.0.213/wallaby/node_modules/ws/lib/PerMessageDeflate.js:249
at afterWrite (_stream_writable.js:484)
at onwrite (_stream_writable.js:475)
at InflateRaw.afterTransform (_stream_transform.js:96)
at Zlib.processCallback (zlib.js:571)
The moment it throws these, it stops working until restart.
(I am not 100% sure but it happens usually when I click on a preview tab where there's no code)
I hope this helps
@ArtemGovorov I played with it, and now I can reproduce 100%:
Wallaby.js: Show Last Screenshot
I can see the. error on the console, and wallaby ui stops working
@dzsodzso63 Thanks for providing more details! The issue is fixed and the fix is published in the latest Wallaby VS Code extension v1.0.214.
Issue description or question
Wallaby stop reporting test results on IDE, No results change in VSCode, no visible color annotation, text, and the
Wallaby.js Tests
output shows an outdated output The only place I can see the test has run, is theWallaby.js Console
output (After changing a test file)If I run
Wallaby.js: Start
command, it works againWallaby diagnostics report