-
Notifications
You must be signed in to change notification settings - Fork 60
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 message when access is done with wrong password #12
Comments
Will check this next weekend when I have access to the hardware. |
I can't replicate that error on the 1.0 branch but I do have trouble connecting even with the correct password from the CLI
|
On the same system, in Python itself I can usually connect but get a different exception.
|
Seems the box is unable to read the description files. May be a side effect of removing lxml. I can go to this by end of the week. Sorry, no sooner. Should set up a VPN then. |
I suppose I found it – at least in theory: the documentation of This and Christians topic are two different issues. |
Agreed. I think there are two separate additional issues: the transient one relating to model name (I've had this in the CLI and in the Python shell) and the service description thingy. I'll create some tickets and see if I can run some low level tests for more meaningful data. |
There have been some subtle issues left in error raising. Is fixed now by 21499f7 |
When I try:
I get a trace back error:
Traceback (most recent call last):
The text was updated successfully, but these errors were encountered: