Skip to content
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

Send Dispatch ID with RunRequest #24

Merged
merged 1 commit into from
Apr 17, 2024
Merged

Conversation

chriso
Copy link
Contributor

@chriso chriso commented Apr 17, 2024

When function calls are dispatched through a DispatchService, the service returns a dispatch_id for each call.

This identifier is never shown again to the user; they have no way of knowing which requests correspond to that function call.

This PR resolves the issue by attaching the same dispatch_id to each RunRequest.

@chriso chriso requested review from achille-roussel and Pryz April 17, 2024 05:37
@chriso chriso self-assigned this Apr 17, 2024
@chriso chriso merged commit 167bd36 into main Apr 17, 2024
3 checks passed
@chriso chriso deleted the dispatch-id-on-run-request branch April 17, 2024 05:38
chriso added a commit that referenced this pull request Apr 17, 2024
In #24 we added
`RunRequest.dispatch_id`, to allow clients to link requests back to a
particular call dispatch.

When a function calls other functions via `Poll`, clients have no way to
link the children back to their parent calls.

This PR adds additional fields that allow clients to reconstruct the
call hierarchy as requests are handled.

I've explicitly left out a `PollResult.dispatch_ids`, so that there's no
confusion between the usage of these identifiers vs. the correlation IDs
that users currently use to link call results back to their original
calls.
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