Fixed number parsing for --port.#153
Conversation
|
Hey @Windows81, thanks a lot for the contribution! Before we can accept your changes, please sign the Eclipse Contributor Agreement (ECA) with the same email that was used to create the commit. This is a simple CLA that simply keeps legal trouble out of the way :) This will also automatically pass the check on your other PR over at #154. |
|
I took a look at it. However, as this is my first time contributing, I need to make an account with Eclipse. Problem is that I'm not currently able to get the CAPTCHA to validate properly. My email address is nastyahmede@gmail.com in case that's needed. |
|
Have you signed the ECA with |
|
Thanks for the clarification. I actually haven't properly signed the commit with either. Hold on. |
|
@Windows81 Did you have a chance to try it again? |
|
Might try again soon. |
|
@Windows81 Any updates? I'll close the PR (and #154) at the end of the week unless we can fix the ECA issue. |
|
Hi. Soon after your last reply, I tried to make an account again, but the same problem occurred. I was still unable to make the account. I'll go ahead and try again soon. |
|
I signed it. However, because I used the wrong email address, I'll need to get that changed. Thank you for your patience. |
|
@msujew: I changed my Eclipse account's email address. Eclipse does not allow email addresses to contain dots. However, the address on my commit does have these dots. Please review. |
That is news to me? My email associated to my eclipse account does contain a dot. I don't think that's the issue.
Then please amend the email address on your commit to use the same email that was used to sign the ECA. Unless the ECA check passes, we won't be able to merge the PR. |
b28e8d2 to
c7defec
Compare
Signed-off-by: VisualPlugin <aboshadinahmed@gmail.com>
|
I made sure that the email addresses for commiter, author, and Eclipse account all match. I'll give the site some time to update. |
|
@Windows81 Thank you, the ECA now works. I'll take a look at the changes in the upcoming days. In the meantime, do you mind fixing the linting and build errors (as seen in the CI)? |
|
There are still linting and build errors in the changes. |
|
Superseded by #167. |
Normally, utilising
oct-server -p 81will print the message:This pull request attempts to fix that.
Refer to https://www.npmjs.com/package/commander#custom-option-processing for this implementation.