David Baker a15c8fd476 Only limit the rageshake log size in one place ... We had two different places in the code that were both trying to limit to the MAX_LOG_SIZE and doing different things with it. fetchLogs was keeping each individual file to MAX_LOG_SIZE but then the outer loop was also discarding the whole file if it would make the total exceed MAX_LOG_SIZE. This meant that if you ran your client for a while then refreshed and sent a rageshake, the logic would omit everything from before the refresh but make sure it included the tiny amount of useless logging from after the refresh. This will truncate large files if they would take the whole thing over the size limit and still include part of them.		2019-10-04 14:56:46 +01:00
..
rageshake.js	Only limit the rageshake log size in one place	2019-10-04 14:56:46 +01:00
submit-rageshake.js	Fix some more lint errors	2018-10-11 22:06:01 -05:00