-
Notifications
You must be signed in to change notification settings - Fork 61
login failed with go runtime error #27
Comments
Thanks for investigating and hunting down the error! |
Silent login fail error handling (#27)
Did you use your "normal" internet connection or some kind of vpn or proxy? |
Yes, 100% vanilla direct connection. Actually I think the rate limiting occurred before that:
You know the rest of the story :) I suspect the rate limiting was the reason of the ep failure but maybe the downloader code part interpreted the fails as a not logged in situation... At least with the PR, user will try to login again and he will have the actual HTTP code (for logging in). I think the same enhancement of error handling could be done on the downloader part too. At least now, no more runtime panic ! |
By poking around in the code, I found out that login queries where denied (most likely by cloudflare) with
429 Too Many Requests
and returned body was empty, preventing the casting of non present values.I will send you a PR handling such cases.
The text was updated successfully, but these errors were encountered: