-
Notifications
You must be signed in to change notification settings - Fork 4
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
Error 213 and UnicodeEncodeError #115
Comments
Ok, interesting things going on:
Could you try to get a manual HTML dump, maybe by uncommenting line 134 in browser.py? Also could you post the output of |
Debug result with HTML-dump (apparently I have no permission to use Kotnet :P):
|
Also, sometimes I get the error above, but other times I get |
Ok, seems like rc 213 is the KotNet equivalent of the recently discovered rc 214 CampusNet code (issue #113 ). Still weird that you get this rc code, though. Not sure, but maybe it has something to do with the "a-number"? Do you get the errorcode when logging in via a webbrowser (with your r-number)?
Nope, you get this error message because one of the connection requests timed out. The timeout for all server connections is set in |
A closer look reveals the likely cause of your rc code:
As in, you're using the
Let me know if that fixes it... |
Ok, I was somehow convinced I needed For the timeout value: maybe it's better to take a waterfall approach? So, every time it fails the timeout is doubled until a max is reached and when it fails even with the maximum timeout the error is raised. |
Nice. We might consider changing the standard prompt to make the default choice more clear.
As far as I see, it's better to grant the maximum timeout at once. The above approach only increases the end user's waiting time, without additional benefits -- the maximum timeout is granted in the end anyway. |
@Wouter92 As for the UnicodeEncodeError, I cannot (for now) find a clean and portable way of fixing this in the source code. The behaviour can be adjusted via the export PYTHONIOENCODING=utf-8 |
Done 5a49dc9 |
Encoding the HTML string in utf8 before passing it on to the communicator for printing should fix issue #115.
@Wouter92 Could you verify whether recent commit f71b37f fixes the Unicode erorrs on you system? Running |
From @Wouter92 :
The text was updated successfully, but these errors were encountered: