-
Notifications
You must be signed in to change notification settings - Fork 125
error code 10100 (auth: invalid) #49
Comments
Hello! |
Thanks @alexeykarnachev! I'm working on it already, tho. It should be deployed in the next few hours. The thing is, we need to move the authentication to the connection class, because we'd have to otherwise hold a reference to the client in connection, which just isn't very nice to look at. If you have a better suggestion, don't hesitate to share! |
It's not as pretty as I'd like - the whole way the resubscription is being handles could be better, but the above commit should fix the issue nonetheless. I / we should perhaps look into a better way to implement this. Could you verify this is working now @lucasjota , @alexeykarnachev ? Use the |
Cool. I'll check it in next hour, but I need a way to simulate an authintification lost. Any ideas? |
..authenticate with the api, pull the ethernet cable and reconnect it again? :'D That'd be easiest I can think of for an interrupted connection. I think that would work. |
Just tried it: |
Oh, ok =) It's because there is no such code in codes dict. UPD: UPD2: auth_sig = hmac.new(self.secret.encode(), auth_string.encode(), hashlib.sha384).hexdigest() I can not find hmac and hashlib in imports. |
Yes, that's because I'm a nugget and forgot them. fixed that. |
Tried it again, |
Here is another thing which looks like a bug: connection.py (262:266)
self.key and self.secret does not exist. Maybe, ".self" should be removed ? |
of course they should be. I don't know what's going on with me today. You make a great debugger, tho ;D |
Hmmm.
I Think it could be fixed by changing if list_data: to ifels list_data: And of course don't forget to add json.dumps(payload) |
looking back, probably wouldve been faster if you had implemented it - I'm coding with my ass today. Fixed that! |
Ok, sure. |
Hello!,
When receiving this error, connection keeps working but only for unauthenticated channels.
Patched it like this:
So it is possible to check and solve from
BtfxWss
instance if wanted/necessary:After reconnect, all keeps smooth again.
Best Regards,
The text was updated successfully, but these errors were encountered: