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

[Task architecture] - Make TaskState object safe #3208

Closed
Tracked by #3191
ss-es opened this issue May 22, 2024 · 0 comments · Fixed by #3133
Closed
Tracked by #3191

[Task architecture] - Make TaskState object safe #3208

ss-es opened this issue May 22, 2024 · 0 comments · Fixed by #3133

Comments

@ss-es
Copy link
Contributor

ss-es commented May 22, 2024

What is this task and why do we need to work on it?

To make stopping/restarting tasks more uniform, the TaskState trait needs to be made object safe.

What work will need to be done to complete this task?

There are a lot of constraints imposed by existing code (particularly our integration tests), and a large part of the work will be disentangling the varying implementations of the existing TaskState trait that are currently spread throughout our code for various different kinds of tasks.

Are there any other details to include?

No response

What are the acceptance criteria to close this issue?

TaskState is object safe.

Branch work will be merged to (if not the default branch)

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant