[$60] Review - Issues get stuck in creating phase

[jmgasper]

Recently, there was a challenge API outage that meant that challenges weren't getting created for new issues for an extended period (>12 hours). We retry a few times to create the challenge, but when the retry limit is exhausted, we still have the issue in the creating phase, which means that it can't be cleared out or tried again. The only solution is to restart the processor to clear out the in-memory cache of issues being created.

Ideally, once a ticket fails to create a challenge, we should remove any temporary status, allowing the user to retry it by closing / reopening a ticket.

[jmgasper]

@afrisalyp - We have fixes in for this, but can you take a look as well just to make sure there weren't any side effects? If we find anything, I'll create a separate ticket, thanks. I'm nervous that the implementation wasn't done real well and the reviewers may not have caught things.

[jmgasper]

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

This is an automated message for ghostar via Topcoder X

[jmgasper]

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

This is an automated message for ghostar via Topcoder X

[afrisalyp]

@jmgasper

I've tested to simulate the scenario by disabling my network connection during creating a challenge. After the creation process was failed, I activated my network connection again and then I closed and reopened the issue. I found that the processor will retry to create the challenge and it was created successfully.

So I confirm that the process works well so far.

[jmgasper]

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

This is an automated message for ghostar via Topcoder X