Raise 'RPC results should only happen after a request was sent'

[MuallimCh]

Raise 'RPC results should only happen after a request was sent'

[Lonami]

Awesome! ^^

[Lonami]

Yes, I've just stumbled on the same problem. I'm not sure if we can safely ignore this error. I've thought of two options:

1. Keep an internal buffer, and if an RPC result is received when receiving updates, simply ignore it. Then it will be read if a "real" request (one we made) is used.
2. Simply ignore it. Some RPC results don't require a MtProtoRequest (which is why the error is rose, because some do require a request, so it can be marked as confirmed). However, I'm not sure if we can simply happily do this, because it may be a result that confirms a request, yet I don't think it's the case: if we sent a request, the updates thread is (should have been) stopped.

[Lonami]

Could you please test @MuallimCh? I'm not able (neither know how) to reproduce this error. I've tried sending a lot of messages very quick, and found a new bug (with the locks) which is now solved.

[MuallimCh]

OK, I will tested it and report you.

[Lonami]

Thanks a lot!

[MuallimCh]

Yes. It fix, please consider close issue. Thx.