-
Notifications
You must be signed in to change notification settings - Fork 27
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
fix: add timeout options when exec arp #13
Conversation
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.
Thank you for your PR and help @howel52. I have just one thing I'd suggest to change.
@DylanPiercey Do you agree with the value for the timeout? Edit: and we might need to think about a way developers can define the timeout and maxBuffer themselves. But that's most likely out of scope of this PR.
Co-Authored-By: Stefan Natter <[email protected]>
yeah, I think developers define the options by themselves is right. And now, In this PR, I have modified the code for suggestions on code review. @natterstefan |
@howel52 thanks for this PR, it looks great 🙂. I agree with @natterstefan that this should be configurable, but it isn’t absolutely required that we do that in this PR. This change will of course require a major release since the current default timeout is effectively |
I want to know when this PR can be merged. And when will the new npm package be released ? |
Hi @howel52. I have just merged it, but it's up to @DylanPiercey to release a new version of the package. @DylanPiercey we could then probably also include (merge+release) this PR: #9. |
thx :) |
#12