Skip to content

on ctx.run() the sdk flushes both "RunCommand" and "RunNotification" after the run closure done execution #72

@muhamadazmy

Description

@muhamadazmy

The run time expects to receive RunCommand when the run closure is about to start executing. Then receiving the completion notification when the run finishes running. This is how it is implemented in all SDKs (typescript, python, etc..) but not how it happens in rust.

In rust both the command and the notification are received when the run context finishes execution this causes the UI to render the ctx.run() as a zero (or microseconds) width span. Same for tracing.

While this not a blocker it would be nice to fix this to be aligned with the remaining SDKS and to give proper representation on both UI and tracing

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions