-
Notifications
You must be signed in to change notification settings - Fork 7.6k
add a timeout to test-connection #2492
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 a timeout to test-connection #2492
Conversation
Hi @jpsnover, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution! TTYL, MSBOT; |
jeffrey and I spoke about my comments - the current timeout is 1000 ms, so this does not change our current behavior and provides for more flexibility |
@@ -128,6 +128,14 @@ public class TestConnectionCommand : PSCmdlet | |||
public Int32 BufferSize { get; set; } = 32; | |||
|
|||
/// <summary> | |||
/// The following is the definition of the input parameter "BufferSize". | |||
/// Buffer size sent with the this command. The default value is 32. | |||
/// </summary> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this comment does not seem to apply
I'd love to see additional tests here -
something along those lines |
Your committer email (private@jsnover.com) appears to be connected to the @jsnover GitHub account, and not the @jpsnover GitHub account you opened the PR from (so the commit doesn't "belong" to @jpsnover as far as GitHub is concerned). Do you mean to use this email for you commits, and if so, is it possible to verify it with your current @jpsnover GitHub account? |
@andschwa I've made it so hat private@jsnover.com is the only account connected to my jpsnover github account. |
/// Time-out value in milliseconds. If a response is not received in this time, no response is assumed. The default is 1000 milliseconds. | ||
/// </summary> | ||
[Parameter] | ||
[ValidateRange((int)1, Int32.MaxValue)] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've never liked this use of ValidateRange
- it seems like we should have ValidatePositive
and ValidateNonNegative
attributes.
This replaces PR #2479