-
-
Notifications
You must be signed in to change notification settings - Fork 181
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
Can + 1 operate when the port is occupied #250
Comments
I'm not sure whether this is a desirable feature or not, but just in case you weren't aware you can do |
Thank you very much for your reply. I'll try it |
Hey @Jeffrey-mu, thanks for trying Bud! As @jfmario mentioned, you can manually change the port, but I'd definitely like to add support for this. I run into this quite a bit during development. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
close |
close |
Re-opening since we'd still like to do this one. |
哦 That's great! |
* increment port * limit port * gofmt * remove debuggy print statements * broken test * 3001 * move logic and testing into the socket packages * fix comment Co-authored-by: EC2 Default User <ec2-user@ip-172-31-40-12.us-east-2.compute.internal>
| listen tcp 127.0.0.1:3000: bind: address already in use
For example, running on
127.0.0.1:3001
| listen tcp 127.0.0.1:3001: bind: address already in use
127.0.0.1:3002
The text was updated successfully, but these errors were encountered: