Can this issue be reproduced with the latest version?
Yes
Steps to reproduce
**1. Receive a message from another User
Read it
Wait until another user edited this message
You will receive update about message edit only when another pts-changing update arrive (for example, new message, but not online status)**
As I understand from logs, it happens because of some attempt of the library to fix update sequence:
{"level":"debug","ts":1715867034.0408983,"logger":"pts","msg":"Gap detected","gap":[{"from":4416,"to":4417}]}
{"level":"debug","ts":1715867034.0409162,"logger":"pts","msg":"Out of gap range, postponed","upd_from":4418,"upd_to":4418,"gaps":[{"from":4416,"to":4417}]}
What version of gotd are you using?
Can this issue be reproduced with the latest version?
Yes
Steps to reproduce
**1. Receive a message from another User
As I understand from logs, it happens because of some attempt of the library to fix update sequence:
Here is the minimal example to reproduce it:
What did you expect to see?
Update passed to handler immediately after arriving
What did you see instead?
Update passed to handler only when another update arrives
What Go version and environment are you using?
go version go1.21.1 darwin/arm64
go env