This repository was archived by the owner on Mar 13, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 16
Pending tickets #79
Comments
jmgasper
added a commit
to topcoder-archive/topcoder-platform-topcoder-x-processor
that referenced
this issue
Sep 25, 2018
jmgasper
added a commit
that referenced
this issue
Sep 25, 2018
jmgasper
added a commit
to topcoder-archive/topcoder-platform-topcoder-x-processor
that referenced
this issue
Oct 2, 2018
topcoder-archive/topcoder-platform-topcoder-x-ui#89 (major requirement) topcoder-archive/topcoder-platform-topcoder-x-ui#88 (major requirement) topcoder-archive/topcoder-platform-topcoder-x-ui#87 (major requirement) topcoder-archive/topcoder-platform-topcoder-x-ui#86 (major requirement) topcoder-archive/topcoder-platform-topcoder-x-ui#83 topcoder-archive/topcoder-platform-topcoder-x-ui#82 topcoder-archive/topcoder-platform-topcoder-x-ui#74 topcoder-archive/topcoder-platform-topcoder-x-ui#71 topcoder-archive/topcoder-platform-topcoder-x-ui#35 (major requirement) topcoder-archive/topcoder-platform-topcoder-x-ui#79 (major requirement) topcoder-archive/topcoder-platform-topcoder-x-ui#76
jmgasper
added a commit
that referenced
this issue
Oct 9, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If there are multiple pending tickets at the same time, while we wait for them to have challenges created, they go into the mongoDB with a null challengeID. The problem is that the challengeID is an index, so that causes a collision / duplicate key error:
We should fix the index so that the challengeID isn't required.
The text was updated successfully, but these errors were encountered: