Rewrite Error message Address in use #485#487
Conversation
|
Thanks! You'll probably want to use There needs to be a test written. Starting up one daemon before trying to start a second should be enough to make the failure case happen. Is this the only error message that could be thrown by |
|
Thanks for your pointers. I did the pull request so early, because I had not noticed that pushed commits that reference an issue got a link in the issue thread, to get feedback. I plan to look at Mojo source to see how and what messages throws when dies as I have noticed that this particular message has parts that depend on $ENV{LANG} . I will also create a test for it on t/command/daemon.t I suppose that it is OK to include in the pull request both files and all chain of commits, isn't it? |
|
This seems like it's a single change, so it should likely be a single commit. So you can amend your current commit, and then force-push to update the pull request. Otherwise, I can squash the commits when I merge, either way. |
"Can't create listen socket: Address already in use" is rewriten as "Can't create listen socket for (http://*:3000): Address already in use" it changes all "Can't create listen socket:" messages to "Can't create listen socket for ($listen_URL):" It has a test in t/command/daemon.t that test the new messge when no port is specified Signed-off-by: Jose Luis Perez Diez <jluis@escomposlinux.org>
|
I messed the pull request a little as I don't use normally amended commits. |
|
No worries, we can clean up the commits later. Let me know if you've got any questions. |
fe08738 to
8fa1abd
Compare
"Can't create listen socket: Address already in use" is rewriten as
"Can't create listen socket on port $port: Address already in use"
Signed-off-by: Jose Luis Perez Diez jluis@escomposlinux.org