Lonami

> Maybe the telethon can use other way for check the connection when receiving msg，The current strategy seems checking the receiving bytes Telethon does not intentionally check just whether the...

You need to provide the necessary code, preferably under 100 lines long, and steps needed to reproduce the issue.

As I've said before I've been unable to reproduce the issue myself so it's hard for me to reliably trigger it and try to diagnose it. Someone that experiences the...

> I can provide a VPS with this problem. You can [message me privately](https://t.me/Lonami), with a link to this issue so I know you are not spam. Then depending on...

I believe the idea behind that is that, after enough failures, the library would give up. But, maybe it's fine to always raise on unknown errors. Feel free to send...

The traceback seems cut, as the error is missing. Could you provide the full error log? v1.28 did introduce some changes to the cache of entities, but the traceback doesn't...

That's the first time I'm seeing the above error. What does it show when you do the following?: ```python print(await client.get_input_entity(channel_id)) ```

For some reason, you seem to have the same ID in the cache with and without the mark. What does it show if you `print(self.session._entities)`?

It might also be interesting to print the traceback and objects in https://github.com/LonamiWebs/Telethon/blob/07a7a8b4045dc60f733f8ebe5ced0bdf6ce721ac/telethon/sessions/memory.py#L150-L151, so that we know what is causing those to be saved that way: ```python def process_entities(self, tlo):...

Nevermind, the above isn't gonna work.