Jump to content

Github Contributors & Runtime Logs


Kyet

Recommended Posts

We recently started publishing the public runtime summary log.

That public log:

  • Shows basic information about every runtime error that happened on the live server last round.
  • Is intended to help PR authors identify and fix runtime errors in our codebase.


Now we are going further, and giving Github Contributors access to the full day server runtime log.

This is the same runtime log that previously only staff (e.g: staff coders and admins) had access to.
This new log:

  • Is much more detailed than the public log, providing a full stack trace for every runtime error.
  • Covers a larger window of time, being an almost identical copy of the live server's runtime log for the whole calendar day up to present.
  • Has a few safeguards to protect certain information (like player IP addresses) but otherwise provides all the information we have on runtimes.
  • Is updated at the end of every round, new information being added at the end.
  • Is reset at the end of every calendar day (since it only includes information from the current calendar day).

 


Alongside these changes:

  • "Github Contributor" is now a role on the website, which means if you are one, that will be listed under your avatar when you post on the forum. Having the role on the website is also necessary to access the new contributor-only runtime log.
  • All players who already have the Github Contributor role in Discord, and who have linked forum accounts, have been granted the role on the website as well. If you are one and did not get it, that means you haven't linked your forum/discord accounts. Do that, then message me.
  • Similarly if you've got a good record of contributing to the github and don't have the Github Contributors role, then message me.
Edited by AffectedArc07
New URL for runtime_summary
Link to comment
Share on other sites

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Terms of Use