Remove leaking abstractions in policies.py
Bug #1828000 reported by
Renat Akhmerov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Confirmed
|
Medium
|
Renat Akhmerov |
Bug Description
RetryPolicy class in policies.py has to check whether the task is "join" or not to handle its state correctly and schedule a job to refresh its state.
We need to refactor it so that policies don't rely on the knowledge of a particular workflow type.
Changed in mistral: | |
milestone: | none → train-2 |
Changed in mistral: | |
status: | New → Confirmed |
assignee: | nobody → Renat Akhmerov (rakhmerov) |
Changed in mistral: | |
milestone: | train-2 → ussuri-1 |
importance: | Undecided → Medium |
Changed in mistral: | |
milestone: | ussuri-1 → ussuri-2 |
Changed in mistral: | |
milestone: | ussuri-2 → ussuri-3 |
Changed in mistral: | |
milestone: | ussuri-3 → victoria-1 |
summary: |
- Remove leaking abstractions + Remove leaking abstractions in policies.py |
Changed in mistral: | |
milestone: | victoria-1 → victoria-2 |
Changed in mistral: | |
milestone: | victoria-2 → victoria-1 |
Changed in mistral: | |
milestone: | victoria-1 → wallaby-1 |
To post a comment you must log in.