Closed agrare closed 1 year ago
@Fryguy Is it possible to raise the priority of this bugfix? Or are we thinking the deleted_on logic is not critical?
@kbrock we'll backport to petrosian as part of the set, yes. Even so, we'll need to deal with existing records anyway.
Rebase please. I think kubernetes HEAD fixes this issue
Backported to petrosian
in commit 7793ce09194180ee171d172d73f9de22c95afdbb.
commit 7793ce09194180ee171d172d73f9de22c95afdbb
Author: Keenan Brock <keenan@thebrocks.net>
Date: Fri Jul 14 16:09:47 2023 -0400
Merge pull request #496 from agrare/fix_started_at_finished_at_timestamps
Fix started_at/finished_at always being nil
(cherry picked from commit 1c753fe979d1ecec638b211d88f9ff7af8d8ed92)
The
state_info
had symbol keys like:startedAt
and:finishedAt
and we were looking for string keys like"startedAt"
and"finishedAt"
causing these values to always benil
even if data existed in the API response.