In the TestCafe documentation the skipUncaughtErrors flag mentions: uncaught error or unhandled promise rejection occurs on the server during test execution.
What is meant by server here?
I found this flag after we started getting an issue quite randomly, with very little to debug from:
1) - Error in fixture.beforeEach hook -
Unhandled promise rejection:
Error: [eval("")] Not JSON response
at exports.newError
Figured it was worth a try to set skipUncaughtErrors: true and we haven't seen that issue since. Nonetheless, the team is worried about using features we don't understand. :)
The server word here means a NodeJS process where test code is executed. So, any uncaught error or unhandled promise rejection that occurred in test code will be ignored by TestCafe if the skipUncaughtErrors option is enabled. For more details about TestCafe architecture, refer to the following topic in the TestCafe documentation: https://devexpress.github.io/testcafe/documentation/how-it-works/#client-server-architecture
Related
I'm sorry, I was able to get this all to work yesterday, but I can't get Expo to attach to my VS Code Debugger today, with various problems.
At this moment I have no server running. Expo is open in my simulator. I hit "run" on "Debug in Expo" from VS Code and I get this error:
(node:16799) UnhandledPromiseRejectionWarning: Error: `fsevents` unavailable (this watcher can only be used on Darwin)
at new FSEventsWatcher (/Users/TuzMacbookPro2017/Development/QMG/Learning/Tuz1App/node_modules/sane/src/fsevents_watcher.js:41:11)
at createWatcher (/Users/TuzMacbookPro2017/Development/QMG/Learning/Tuz1App/node_modules/jest-haste-map/build/index.js:780:23)
at Array.map (<anonymous>)
at HasteMap._watch (/Users/TuzMacbookPro2017/Development/QMG/Learning/Tuz1App/node_modules/jest-haste-map/build/index.js:936:44)
at _buildPromise._buildFileMap.then.then.hasteMap (/Users/TuzMacbookPro2017/Development/QMG/Learning/Tuz1App/node_modules/jest-haste-map/build/index.js:355:23)
at processTicksAndRejections (internal/process/next_tick.js:81:5)
(node:16799) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:16799) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[Error] Error: Could not start the packager.
Let's start the server and see what happens...
Server loads, all good. I haven't selected "Run" from the Metro screen.
Let's try running the debugger again and see what happens...
Error: listen EADDRINUSE: address already in use :::8081
at Server.setupListenHandle [as _listen2] (net.js:1256:14)
at listenInCluster (net.js:1304:12)
at Server.listen (net.js:1392:7)
etc...
Makes sense, npm is running on port 8081. I can load the project in Expo; when I do, it opens up a chrome debug window. Let's hit "Stop Remote Debugging" and see if we can run the debugger from VS Code again (probably not since the port is still in use. -- right, same error.)
Ok now that we've disabled remote debugging in expo, let's stop the server and maybe try to restart from VS Code? Nope. Simple error:
[Error] Error: Could not start the packager.
Any help? I KNEW I should have written down all the steps I took yesterday!
All of my individual Protractor tests in a given Jasmine spec have passed, but the spec still fails with this message:
Failed: Error while waiting for Protractor to sync with the page: "hooks is undefined"
I haven't been able to find any information on the meaning of "hooks is undefined".
Using
protractor#5.1.2
firefox 57.0.3
There is no stack trace; the full text of the error is as follows:
An error was thrown in an afterAll
AfterAll Failed: Error while waiting for Protractor to sync with the page: "hooks is undefined"
The error can be thrown when protractor tries to interact with a page during the beforeAll, beforeEach, afterAll, or afterEach hook, before angular has loaded on that page. It can be caused for essentially the same reason as "cannot read property '$$testability' of undefined".
A possible solution is to put this in the line above any protractor activity in the hook:
browser.sleep(2000);
And/Or increase the length of an existing sleep in your before/after hook, so that the page has time for angular to load first, before invoking protractor.
Getting error in spinnaker when we start the web-ui.
Get stuck too much. The error i got is:
vendor.bundle.js:9331 Uncaught Error: [$injector:modulerr] Failed to instantiate module netflix.spinnaker due to:
Error: [$injector:modulerr] Failed to instantiate module spinnaker.core due to:
Error: [$injector:modulerr] Failed to instantiate module spinnaker.core.notification.types due to:
TypeError: Cannot read property 'email' of undefined at Object.register
thanks .
What spinnaker version do you run?
Upgrade spinnaker first
perhaps use Minnaker OSS to get started faster for PoC.
I am using bigcommerce stencil and have started working on it and run command "stencil start" and got this error:
Debug: internal, implementation, error
TypeError: Uncaught error:self.assembler.getTranslations is not a
function
Also check in local (http://localhost:3000/) got below error
{"statusCode":500,"error":"Internal Server Error","message":"An
internal server error occurred"}
Can any body help me why I am getting this error?
We are facing a VerifyError in our application while deploying to WAS environment. The following is the exception:
Error 500: org.springframework.web.util.NestedServletException: Handler processing failed; nested exception is java.lang.VerifyError: JVMVRFY012 stack shape inconsistent; class=com/org/jaxb/Input_JAXB_Deserialization_Stub, method=write(ILjava/lang/Object;)V, pc=356
We are still trying to identify the issue, but all efforts not going well. Is there any way that the libraries used in run time is good in bytecode compatibility?. For example, we can add all the libraries and run the byte code verification.