That.Funkencool wrote:@Jools, I'm guessing gajop is (maybe?) thinking about writing some lua that would upload the infologs; but first, he wants to know if there is a service that exists to upload them to.
Whether or not that's the case, you're focusing on the wrong aspect.
That's possible as well, but *some* Spring service needs to receive links to infologs so it can parse it, therefor some kind of API is needed.Funkencool wrote: Maybe this 'code' could upload to pastebin and just attach the link to the replay site somehow for temporary viewing? Then there wouldn't be countless unneeded logs.
That's what I want to do too.Jools wrote:That's what I meant by integrating it in game or lobby (or engine).
Agreed. For crashes widgets are probably unusable. That said, I also want to report non-crashing Lua errors. Even reporting usage statistics (e.g. hardware specs/opengl output) can be useful.Silentwings wrote:They can be sent using a widget, but thats not great since if Spring crashes I can't see a way to guarantee that the stacktrace is sent by the widget after the crash occurs.
Lobby client or anything that launches Spring really. I can imagine that Spring (or a Spring game) could one day come with a process that is launched simultanesouly with it and is used to handle errors. But I digress, (non-Lua) lobby clients are probably the thing that would handle Spring crashes.Silentwings wrote: So probably it has to be sent from the lobby client (automatically or at request of user) and then the replay site would have to do some kind of sorting to match them onto games.
This is certainly a thing to consider. On the client side, the user can be asked a couple of questions such as: "Report usage statistics?", "Report this error that just happened and may have caused a loss in functionality?". Anonymizing can be done on either the client or the server side. The server could have only some infologs be public and others available just to the developers (engine+game).
PS: I've noticed from FA's screens that weblobby has a weblobby.log. I guess most lobbies have their own logs, so some kind of reporting there wouldn't be bad to have. (Same applies for AIs). Maybe this should really be a separate service from the replay site that is integrated with it?