Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better error reporting #84

Open
alkurbatov opened this issue Oct 6, 2018 · 2 comments
Open

Better error reporting #84

alkurbatov opened this issue Oct 6, 2018 · 2 comments

Comments

@alkurbatov
Copy link
Contributor

From @rorschach on Discord:

I don't have an github account,
honestly the one big problem was that if the laddermanager doesnt find the map, it tried to start the game anyways and as "reason for the crash" it looks like there was a timeout or so, but in reality it could not start the game because it had no map
if you read the whole consol output you see it, but when you just look at the end and to see why it crashes it's not clear

Looks like we need to improve error reporting in some way (currently there are lots of messy output) in some way. Probably show only stderr or drop unused info?

Also, I would say, that we need a troubleshooting guide.

@lladdy
Copy link
Contributor

lladdy commented Oct 6, 2018

+1 for this if anyone gets time.
We could probably utilize exceptions to clean up a lot of the error handling and reporting.

@Cryptyc
Copy link
Owner

Cryptyc commented Oct 6, 2018

yeh, its something I'll definately look at after this season of the ladder is over. Really busy with getting the tournament and everything sorted right now though

@Archiatrus Archiatrus mentioned this issue Jan 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants