-
Notifications
You must be signed in to change notification settings - Fork 132
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
provide human friendly error msg for local port forwarding errors #831
Comments
@eyberg how to reproduce this ? |
without running a tap - try running this example https://ops.city/ on the same port twice - you should get this error message complaining that qemu can't listen on the same port since something else is already listening on it - what we'd like is a more developer friendly message - "something is already listening on this port" - we could even go further and show the user what process id it is |
This is what I output from port checking:
currently the checking is using |
Currently, ops isn't supporting windows. Alternatively, windows users can use ops in WSL. |
ah ok, will leave windows for now. |
(closes #831 ) * Added ports pre checking To find out whether they are being used by other applications. * Check which process is using target port, if any * Moved excludeWhitespace() function to util package
we should explicitly tell the user that there is probably something listening on this port already if un-privileged - I would almost go as far as to say we should show which process is listening on it
The text was updated successfully, but these errors were encountered: