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 need a separate error file that logs all requests and responses to the Topcoder APIs (member API, challenge API, etc...)
Right now it's very, very difficult to use the Papertrail log in Heroku to narrow down specific errors that are happening.
The Topcoder APIs are very flaky and prone to random errors, so we need a way to accurately log the requests and EXACT response from the server.
We need to log all:
POST parameters
The URL endpoint called
Any additional headers used (removing the authorization token)
The response code to the call
The response message / JSON received
All of this should be logged as a SINGLE message. Right now we have a hard time separating out the requests and responses and errors because there could be multiple requests happening simultaneously. If we log things as a single message, it will be much easier to obtain the needed information for further debugging.
The text was updated successfully, but these errors were encountered:
We need a separate error file that logs all requests and responses to the Topcoder APIs (member API, challenge API, etc...)
Right now it's very, very difficult to use the Papertrail log in Heroku to narrow down specific errors that are happening.
The Topcoder APIs are very flaky and prone to random errors, so we need a way to accurately log the requests and EXACT response from the server.
We need to log all:
All of this should be logged as a SINGLE message. Right now we have a hard time separating out the requests and responses and errors because there could be multiple requests happening simultaneously. If we log things as a single message, it will be much easier to obtain the needed information for further debugging.
The text was updated successfully, but these errors were encountered: