Change.DoesNotExist: Change matching query does not exist.

[sentry-io]

Sentry Issue: WEBLATE-1NJC

Change.DoesNotExist: Change matching query does not exist.
(4 additional frame(s) were not displayed)
...
  File "weblate/trans/views/edit.py", line 669, in translate
    response = handle_suggestions(request, unit, this_unit_url, next_unit_url)
  File "weblate/trans/views/edit.py", line 585, in handle_suggestions
    old=suggestion.change_set.latest("timestamp").old,

This seems regression caused by #13214

[nijel]

@gersona This is a five-year-old suggestion that didn't yet create matching Change objects. The code should deal with such a situation. Would it be possible to do it without relying on change objects?

[gersona]

oh right, that makes sense. I was starting to investigate how on earth did the Suggestion creation stop before the Change object was created.
Yeah, the unit.target could be used as well . As the suggestion is always relative to the current target, it doesn't matter if it has been updated multiple times since the suggestion was first added

[github-actions]

Thank you for your report; the issue you have reported has just been fixed.

• In case you see a problem with the fix, please comment on this issue.
• In case you see a similar problem, please open a separate issue.
• If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.