Skip to content

Expose duration through DispatchInfo #121

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

Closed
wants to merge 3 commits into from

Conversation

shsms
Copy link
Contributor

@shsms shsms commented Mar 27, 2025

No description provided.

shsms added 3 commits March 27, 2025 17:32
Signed-off-by: Sahas Subramanian <[email protected]>
Some dispatches need the duration to make an execution plan.

Signed-off-by: Sahas Subramanian <[email protected]>
Signed-off-by: Sahas Subramanian <[email protected]>
@shsms shsms requested a review from a team as a code owner March 27, 2025 16:40
@github-actions github-actions bot added part:docs Affects the documentation part:dispatcher Affects the high-level dispatcher interface labels Mar 27, 2025
Comment on lines 32 to +37
options: dict[str, Any]
"""Additional options."""

duration: timedelta | None
"""The duration of the dispatch."""

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just suggestion: duration can be in options dict.
However I don't know why you need this so feel free to ignore this comment.

Copy link
Contributor

@llucax llucax left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Requesting changes to avoid accidental merges until we figure this out.

This solution will not work well in the general case.

@@ -229,6 +232,7 @@ async def _start_actor(self, dispatch: Dispatch) -> None:
components=dispatch.target,
dry_run=dispatch.dry_run,
options=dispatch.payload,
duration=dispatch.duration,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is tricky and can be misleading. If you use the high-level interface and you are listening to the start/stop events, or your actor is managed, this duration might not match the time your actor is really running if some dispatches were merged.

I think a better approach would be to include a list of active dispatches, and just pass the full Dispatch object there. Another approach would be to pass here a "merged duration" instead of the raw duration of the current dispatch. Depending on the use case one could be more useful than the other.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I moved the conversation to #119, I think it is more appropriate to discuss the design in the issue.

@llucax llucax linked an issue Mar 28, 2025 that may be closed by this pull request
@shsms shsms closed this Mar 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
part:dispatcher Affects the high-level dispatcher interface part:docs Affects the documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Pass duration in DispatchInfo
3 participants