[$50] Investigate DB issue not found error

[jmgasper]

@afrisalyp - Seeing this error quite a bit in prod too. Any thoughts on why? I've seen it for both Gitlab and Github tickets.

[jmgasper]

Contest https://www.topcoder.com/challenges/30109220 has been created for this ticket.

This is an automated message for ghostar via Topcoder X

[afrisalyp]

@jmgasper
Can you please provide the details of the ticket activity?
What was the activity before the error comment occur? And how was the ticket going on?
Thanks

[jmgasper]

@afrisalyp - Still seeing this in prod

Here's the activity for a new ticket (errors started happening about 4 minutes after creation):

[afrisalyp]

@jmgasper

I assume that the DB query problem is already fixed.

My investigation so far, topcoder-x-processor receives issue.updated too early before the issue is created in the DB (before issue.created is received). I'll make the process to automatically create the DB record when receive issue.updated. So the next issue.created will be ignored.
Does it sound acceptable solution?

[jmgasper]

@afrisalyp - That sounds like it could be the issue and the solution would make sense.

[afrisalyp]

@jmgasper - It's done. A PR submitted.

[jmgasper]

Contest https://www.topcoder.com/challenges/30109220 has been updated - amunation has been unassigned.

This is an automated message for ghostar via Topcoder X

[jmgasper]

Contest https://www.topcoder.com/challenges/30109220 has been updated - it has been assigned to afrisalyp.

This is an automated message for ghostar via Topcoder X

[jmgasper]

Payment task has been updated: https://software.topcoder.com/review/actions/ViewProjectDetails?pid=30109220

This is an automated message for ghostar via Topcoder X