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.
We shouldn't be trying to cancel any challenges. It was confirmed that this wasn't going to work due to limitations in the challenge API around how challenges are cancelled. I've seen this in the logs recently:
debug: {"status":400,"response":{"req":{"method":"POST","url":"http://api.topcoder.com/v3/challenges/30108188/cancel","headers":{"user-agent":"node-superagent/3.6.0","authorization":"...","content-type":"application/json"}},"header":{"date":"Wed, 27 Nov 2019 23:58:29 GMT","content-type":"application/json","content-length":"173","connection":"close","server":"nginx","access-control-allow-headers":"Authorization,Content-Type,Accept,Origin,User-Agent,DNT,Cache-Control,X-Mx-ReqToken,Keep-Alive,X-Requested-With,If-Modified-Since","access-control-allow-credentials":"true","access-control-allow-methods":"GET, POST, OPTIONS, DELETE, PUT, PATCH"},"status":400,"text":"{\"id\":\"1d9e9bc9:16e0e1e030b:549a\",\"result\":{\"success\":true,\"status\":400,\"metadata\":null,\"content\":\"Close challenge only applicable against ACTIVE challenge\"},\"version\":\"v3\"}"}}
error: Error happened in system
ProcessorError: Failed to cancel challenge. Detail: Close challenge only applicable against ACTIVE challenge
at Object.convertTopcoderApiError (/topcoder-x-processor/utils/errors.js:81:20)
at Object.cancelPrivateContent (/topcoder-x-processor/utils/topcoder-api-helper.js:524:18)
at <anonymous>
at process._tickDomainCallback (internal/process/next_tick.js:229:7)
The text was updated successfully, but these errors were encountered:
We shouldn't be trying to cancel any challenges. It was confirmed that this wasn't going to work due to limitations in the challenge API around how challenges are cancelled. I've seen this in the logs recently:
The text was updated successfully, but these errors were encountered: