Skip to content

fix(taskworker) Update cluster_projects so it can not use pickle #90705

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

Merged
merged 1 commit into from
May 1, 2025

Conversation

markstory
Copy link
Member

Currently, we invoke this task with a list of Project models that are pickled. This has escaped our existing pickle detection logic as all calls to the task are mocked.

This set of changes introduces a new project_ids parameter that will let us not need pickle. Once this has deployed, I'll change the callsites to pass project_ids and deprecate projects usage.

Refs #90681

Currently, we invoke this task with a list of `Project` models that are
pickled. This has escaped our existing pickle detection logic as all
calls to the task are mocked.

This set of changes introduces a new `project_ids` parameter that will
let us not need pickle. Once this has deployed, I'll change the
callsites to pass `project_ids` and deprecate `projects` usage.

Refs #90681
@markstory markstory requested a review from a team as a code owner April 30, 2025 22:00
@markstory markstory requested a review from a team April 30, 2025 22:00
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Apr 30, 2025
@markstory markstory merged commit c89900f into master May 1, 2025
61 checks passed
@markstory markstory deleted the fix-ds-spawn-pickle branch May 1, 2025 15:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants