[$60] Investigate amunation

[jmgasper]

@afrisalyp - I'm seeing this sometimes with prod. This is after our fixes we did. Any idea what that means or why it's happening? Seems to go along with the Failed to get topcoder member id error.

[jmgasper]

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

This is an automated message for ghostar via Topcoder X

[jmgasper]

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

This is an automated message for ghostar via Topcoder X

[afrisalyp]

@jmgasper
I'm pretty sure that the problem is related to the weird dynamodb behavior.
Since we have resolved only the Issue table, other problems might occur related to User and UserMapping table.

I'll add all() function to the scan() method. It will make sure we get consistent data.

[jmgasper]

Ok - going to close this now and will retest with a prod deploy shortly.

[jmgasper]

@afrisalyp - Still seeing this in prod, only when unassigning. Is there something in the messaging generation that's not working?

[jmgasper]

Have a look at the messages here for an example: #273

[afrisalyp]

@jmgasper

We need to find out why the issue prints out amunation username. Somehow, querying to UserMapping always returns the amunation record.

Can you please provide me the DB record in the UserMapping table where topcoderUsername is amunation?

[afrisalyp]

@jmgasper
Thanks for the detailed record data.
The problem might be related to failed previous assignments.

I put null checking and throw an error if the process going to scan users with no criteria. This is why we always get the first record (amunation).

[jmgasper]

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

This is an automated message for ghostar via Topcoder X