-
Notifications
You must be signed in to change notification settings - Fork 5
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
Account not found #53
Comments
cc. @olabini |
I'll look into this. Did you add any debug-printing to see those statements? |
No, I just printed the account->username on several places to see if it was been found. |
Any idea where the specific places were printed that you saw? |
Yes, immediately as you send the storage status message, and you get back that they are too low, and you try to publish: https://github.com/otrv4/pidgin-otrng/blob/master/prekey-plugin.c#L98 Then this func does not get a prekey client: https://github.com/otrv4/pidgin-otrng/blob/master/prekey-plugin.c#L274 And it fails here: https://github.com/otrv4/pidgin-otrng/blob/master/prekey-plugin.c#L85 Around being incorrectly written in the persistent file, Idk when it happen, it just popped out. |
I have not been able to reproduce this - I've added a large amount of printings all over the place to check for it, but it never happens for me... |
@olabini I'll recheck this.. maybe it is something solved. |
I haven't seen this happening again but as we have some other weird bugs; it is worth keeping it open. |
I just got a crash here:
My guess is that this is from a missing PurpleAccount, so probably connected. |
I've added some assertions to the pidgin-helpers file, to make sure all these invariants are always checked. |
I'm quite uncomfortable on all of this refactorings, as it seems like a lot of functionality is getting broken. I'm unsure in which other places it is broken... |
Sorry, not sure what you're talking about on this issue. I just added assertions to make it faster to see when something is broken. |
Well, I'm talking in general. But let's talk about this on the call. |
Have you seen this issue again? |
OK, we haven't seen this issue for a long while. I'll close this issue now. In case it comes back we can reopen, but I don't think it will. |
Sometimes when the UI actions are too fast (you log in and not wait for the publication, and immediately start an OTR conversation), the account is not found and this happens:
No prekey client.
The printing of the account gives:
THE ACCOUNT
z??? `Sometimes as well, the protocol and account are not found for writing the persistent files and this gets writen:
Can it be a threading error?
The text was updated successfully, but these errors were encountered: