Skip to content

Conversation

@antonag32
Copy link
Contributor

Commands can now be stopped after the specified timeout. The default behaviour of no timeouts is kept the same. Users wanting to opt into this feature must set a new DefaultRunner with properly set values.

Related to #70.

Commands can now be stopped after the specified timeout. The default
behaviour of no timeouts is kept the same. Users wanting to opt into
this feature must set a new DefaultRunner with properly set values.

Related to mistifyio#70.
@antonag32
Copy link
Contributor Author

Hello @mmlb, this is the implementation I asked about. What do you think? The original PR had comments about Send and Receive, I have not used those ZFS commands but I think users can choose for themselves whether to timeout said commands or not?

Tried to go for something similar like httpclient or slog which have a default client/logger and users can override them. Ideally instead of overwriting the default they could create a custom one and use it but that would involve bigger changes and I wanted to keep it simple for starters.

@trisk
Copy link
Member

trisk commented Oct 4, 2025

Thanks for this. I think this is fine for a minimally invasive addition without affecting existing interfaces.

@trisk trisk enabled auto-merge October 4, 2025 02:24
@trisk trisk disabled auto-merge October 4, 2025 02:56
@trisk trisk self-requested a review October 4, 2025 20:34
@mergify mergify bot merged commit ab760d5 into mistifyio:master Oct 4, 2025
2 checks passed
@mergify mergify bot removed the ready-to-merge label Oct 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants