chore: fix retry when quality check failed #3698
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Root cause:
Quality-check recovery cleaned up task tracking (including _assignees) before
retrying. The retry path posted the task again but did not restore the _assignees
mapping, so subsequent quality checks could not find the assignee and logged “No
assignee found in _assignees”.
Fix:
Update _post_task to always set self._assignees[task.id] = assignee_id whenever a
task is posted. This guarantees assignee mapping is restored on retries (and any
other reposts), preventing failures in the quality-check recovery flow.
Checklist
Go over all the following points, and put an
xin all the boxes that apply.Fixes #issue-numberin the PR description (required)pyproject.tomlanduv lockIf you are unsure about any of these, don't hesitate to ask. We are here to help!