feat: parameterize delay in use plugin method - #500
Merged
rholshausen merged 1 commit intoJul 23, 2025
Conversation
planetmarshall
force-pushed
the
use-plugin-custom-delay
branch
from
July 17, 2025 11:42
cdaca08 to
68ec687
Compare
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
2 participants
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.
Pass in the completion delay as a parameter to
pactffi_using_pluugin.By default this function is always blocked for at least 0.5s which can be expensive if the plugin is used in a lot of tests. This allows the user to specify an arbitrary delay (even zero) if there are no ill effects.
See Slack thread for context.