Automated Infolog uploading

[koshi]

I've started on a server side python application that will accept uploads: http://github.com/springlobby/spring-infolog

Someone else (Beherith?) please do the infolog parsing in http://github.com/springlobby/spring-in ... backend.py (with the appropriate Table model).

Then we can talk views of the collected data: http://github.com/springlobby/spring-in ... loglist.py / http://github.com/springlobby/spring-in ... /list.html

[koshi]

Turns out I was/am already prepared to upload a lot more on the SL side: unitsync.log, spring settings, ext.txt and script.

[hoijui]

the most useful for devs would probably be, if we could use basic unix tools to crawl through the data: find, grep, sed, awk
so we could get a list of all GFX cards-driver combinations that crashed in the gfx driver, and compare to average appearance rate of the cards in logs.
is it possible to get a comparable level of freedom through a web interface?

[koshi]

it's a python app, you can do whatever you want to with the uploaded zip

[hoijui]

so i will be able to go to the site, and put something like system("find bli bla | sed ta da") somewhere, and get the result?
or is it more like.. i have to write the whole thing in pure python, then ask someone with admin rights on the server to include this code there, and then i will be able to call it through a web interface?

[koshi]

If someone would be stupid enough to allow entering system commands, sure you would
The idea was to have predefined processing of the data and store that in a db backend.
The uploaded zip could be stored alongside so you can download it and do your own processing on it ofc.

[Licho]

Springdownloader already uploads infolog to separated CA service existing for some years.

I will also send it there.
Where can i upload new data?
Or its not done yet?

[Licho]

Btw it would be great to have it mod filtered and also allow to search for lua errors.
We are using infologs to check rare lua bugs.

[koshi]

It's not done yet, so feature set ain't done yet either.
I am looking for someone to do the actual infolog parsing and db model, so anything's possible atm really.

[zwzsg]

What about privacy concerns?

[koshi]

Not a matter of the receiver, on the SL side this is opt in.

[Pako]

I would like to see all my(and others) Lua errors somewhere. Sometimes the game is just too intense to fix bugs right away and it's usually forgotten after the game. I already have countless forgotten bugs to fix.

[koshi]

I'm planning to make a SL release by the end of the weekend with upload capability enabled. Therefore I'll need at least the barebones (which would only accept uploads and list them) version of this app running by then.
If no one wants to run it on the springrts box make something like infologs.springrts.com point to my box.

[Licho]

So where it is installed and how does it work, how can i send infolog?
Can I send desyncs too?
Can I send demos as well somewhere?

[koshi]

It expects a zip like this as input.
You can use http://infologs.springzine.net/upload as a reference.
Url is still subject to change.

[Zydox]

The crash reports now supports the following files in it:

client.txt -> The name and version of the lobby client (i.e. SpringLobby 0.77 msw)
information.txt -> Input from the user when he submitted the report, if any...
infolog.txt -> From the Spring dir
script.txt -> Spring start script
ext.txt -> From the Spring dir
unitsync.log -> From the Spring dir
settings.txt -> Springs settings (location can be found in the infolog)
demo.sdf -> Springs demo file as long as the file is 5mb or less (location can be found in the infolog)

These are the names which the files need to have inside the zip archive

[Satirik]

the list website misses a lot of <br> in settings list etc