bad_msg_notification are not handled correctly

[Lonami]

I know there's a TODO already, but this is bad: https://github.com/gram-js/gramjs/blob/a5b9864c5d027a806ffa3af1c25bc45641ae4434/gramjs/network/MTProtoSender.js#L570-L577

This is prone to causing 4865 bad_msg_notification before Telegram errors with 429 Too Many Requests at the transport level.

[mannguyen0107]

@Lonami I wanted to help with this would you mind sharing how do I setup a case to replicate this and handle this? Maybe point me to the telegram doc that talk about this would be very helpful.

[Lonami]

I personally would try to inject some code to "skip" handling a message at a desired point (for example the 100th message or when a file exists), and then confirm it fails. Once that's in place a workaround can be developed. I do not know which part exactly talks about this, the best I remember is https://core.telegram.org/mtproto/service_messages_about_messages.

[mannguyen0107]

Thank you I will put this on my todo list once I finish with adding convenience event handlers @painor can you assign this issue to me so I wont forget thank you!