Conversation
Update unit tests
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
pingoption toProcedure.call(). When set to a number, this is the number of milliseconds it will wait for a valid pong before making the call. Useful when the Procedure is expected to take a long time to respond to a call to shortcircuit the waiting time if the endpoint is down. By defaultProcedure.call()will not ping the endpoint.staticmethodProcedure.ping(), which can be used to manually ping an endpoint. If endpoint is not aProcedureor times out waiting for a response, will returnfalse. Useful for when you wish to make multiple calls to an endpoint in relatively quick succession - rather than pinging each time, you can merely ping once before the first call.timeoutoption ofProcedure.call()will no longer be ignored when thesignaloption is set - instead the Promise will be rejected when either it times out or the signal is aborted.0andNumber.MAX_SAFE_INTEGERfor sanity purposes, except when they areNaNor +/-Infinity- in these cases they will never timeout.Procedureinstances:data. Will be fired whenever theProcedurereceivesdataand will be passed the input data. This is mainly useful for additional monitoring and logging, as the input data will already be passed to theProcedure's backing callback.