-
Notifications
You must be signed in to change notification settings - Fork 33
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
Add error if emulator is already running #108
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Instructions
Thrown errors when the emulator is already running are not very explicit by nature. For instance if I attempt to run the kitty-items tests with the emulator already running, the error I see is
thrown: undefined
. This is can be very confusing as evinced by #89 .(Optional): Suggest A Solution
Add some sort of exception handling related to emulator already running, throw an error that is more explicit.
The text was updated successfully, but these errors were encountered: