You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 13, 2025. It is now read-only.
When creating issues in Github or Gitlab it seems that failures to parse the ticket title cause the processing of the ticket to requeue. This puts the status field on the mongo record to challenge_creation_pending. Once that's set nothing gets updated. The only solution has been to:
clear any assignees
clear any TCX labels
delete the record
wait for the processor to catch up
reset the Open for Pickup label
after that everything seems to work. The only thing I've been able to tease out of the logs is a failure to parse the title prizes. Often existing or new bugs come in without prizes set before a ticket is opened and I think that might be a root cause.
The text was updated successfully, but these errors were encountered:
@jmgasper@cwdcwd if there is no prize the issue is discarded from processing, so it shouldn't in be db with suc status. There must be some different steps to replicate this?
@veshu - Yeah, let's make sure the issue is discarded from processing. Are you sure it won't be attempted to be added back later if the labels are changed or an assignee is changed later on? Please make sure to test this one quite a bit - it's been a bit of a thorny issue the last couple weeks.
When creating issues in Github or Gitlab it seems that failures to parse the ticket title cause the processing of the ticket to requeue. This puts the
status
field on the mongo record tochallenge_creation_pending
. Once that's set nothing gets updated. The only solution has been to:after that everything seems to work. The only thing I've been able to tease out of the logs is a failure to parse the title prizes. Often existing or new bugs come in without prizes set before a ticket is opened and I think that might be a root cause.
The text was updated successfully, but these errors were encountered: