Skip to content

[FEATURE]: Task progress metadata from client to server. #224

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
aradu-atlassian opened this issue Jul 30, 2024 · 1 comment
Closed

[FEATURE]: Task progress metadata from client to server. #224

aradu-atlassian opened this issue Jul 30, 2024 · 1 comment
Assignees
Labels
question Further information is requested

Comments

@aradu-atlassian
Copy link
Contributor

Please read our contributor guide before creating an issue.
Also consider discussing your idea on the discussion forum first.

Describe the Feature Request

I would like to add support for a progress percentage, and a progress message to be propagated from conductor client to conductor server when the extension of the lease process happens. We've successfully done this internally by adding a parameter that can be allowlisted for propagation on the update call, but would like to make this as part of the core functionality (Our existing solution requires us to override the WorkflowExecutor and a series of methods and we'd like to avoid this).

This value is used by us to show how far the task is estimated to be, which is especially useful for longer lived tasks. The message is used to report back to end users.

Describe Preferred Solution

Update TaskResult to add new optional proto fields for task prorgess percent, and task progress message.

Update the WorkflowExecutor.extendLease to propagate the progress percent and messages when persisting the lease extension.

Describe Alternatives

An alternative to this, would be to just start propagating all of the outputs provided in TaskResult on lease extension.

@aradu-atlassian aradu-atlassian changed the title [FEATURE]: [FEATURE]: Task progress metadata from client to server. Jul 30, 2024
@jeffbulltech
Copy link
Collaborator

👋 Hi @aradu-atlassian

We're currently reviewing open issues in the Conductor OSS backlog, and noticed that this issue hasn't been addressed.

To help us keep the backlog focused and actionable, we’d love your input:

  • Is this issue still relevant?
  • Has the problem been resolved in the latest version v3.21.12?
  • Do you have any additional context or updates to provide?

If we don’t hear back in the next 14 days, we’ll assume this issue is no longer active and will close it for housekeeping. Of course, if it's still a valid issue, just let us know and we’ll keep it open!

Thanks for contributing to Conductor OSS! We appreciate your support. 🙌

Jeff Bull

Developer Community Manager | Orkes

DM on Conductor Slack
Email me!

@jeffbulltech jeffbulltech self-assigned this Feb 27, 2025
@jeffbulltech jeffbulltech added the question Further information is requested label Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants