Skip to content

Conversation

@hookzof
Copy link
Contributor

@hookzof hookzof commented Jul 11, 2021

No description provided.

@hookzof hookzof changed the title Possible fix of https://github.com/xelaj/mtproto/issues/49 Possible fix of #49 Jul 11, 2021
@quenbyako
Copy link
Member

@hookzof according to this description this pr won't work, unfortunately. I'm not sure, need to test it. But i appreciate your work, thanks.

shit, if telegram devs says that mtproto is opensource, why they didn't share simplest mtproto server, we could test it at least...

@quenbyako
Copy link
Member

won't close this pr, until test it

@AmarnathCJD
Copy link

works!
AmarnathCJD/gogram@15631a7

@quenbyako
Copy link
Member

@AmarnathCJD Could you please create Pull request with this chage? Just to have less differences between your fork and origin repo 😉

Also, Could you please create test case, what will happen, if provided prevID will be 1 billion for example?

@AmarnathCJD
Copy link

AmarnathCJD commented Oct 21, 2022

@AmarnathCJD Could you please create Pull request with this chage? Just to have less differences between your fork and origin repo wink

Also, Could you please create test case, what will happen, if provided prevID will be 1 billion for example?

The commit history is broken :( I will try

and if the prevID is 1 B, the GenerateMessageID runs until the value reaches greater than 1B, This solves the msg_seq_too_high (33) a far as i tested

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants