-
Notifications
You must be signed in to change notification settings - Fork 39
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
5.82 TSH crashes as soon as loading up a tournament #769
Comments
Hi! Can you link the tournament you're trying to load please? Thanks in advance Also please note that loading a Challonge tournament may freeze the program for a couple of minutes while it loads |
Thank you for your quick response! The link is here: https://challonge.com/kzv7scvv P.S. this link is a finished tournament and is for test purpose. |
OK, it seems that Challonge has further increased its Cloudfare protection and is causing us to not be able to pull information properly. While I was able to eventually load the bracket, I was unable to get the name of the tournament, and TSH had to hang for around 2-3 minutes upon first inputting the URL. (But then it works just fine) This may also take even longer with a VPN or overall lower bandwidth connection, but from the logs the program had only tried loading the bracket around 20 times before it was closed, instead of either succeeding with the loading or running out of the 150 attempts it tries. For now however, all I can ask is to be patient when loading the bracket. We will look further into this to try and find workarounds, but ultimately having to deal with Cloudfare may force us to drop support for Challonge altogether, and try to find an alternative (besides StartGG which has its own issues) We apologize for the inconvenience. |
Thank you for your response! Guess I'll just wait till TSH to work it's magic for now. |
After updating to 5.82, TSH will crash as soon as I load up a tournament.
It will keep crashing thereafter no matter how many times I restart TSH.
If I just unzip the TSH files and start it up, it's fine.
tsh.log
tsh-error.log
We currently live in china and given the firewall situation, we are using VPN to connect, if this helps.
The text was updated successfully, but these errors were encountered: