You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am sure the error is coming from Pyrogram's code and not elsewhere
I have searched in the issue tracker for similar bug reports, including closed ones
I ran pip3 install -U https://github.com/pyrogram/pyrogram/archive/master.zip and reproduced the issue using the latest development version
Description
Telegram says: [420 FLOOD_WAIT_X] - A wait of 78 seconds is required (caused by "contacts.ResolveUsername")
here is my code that causes the error
peer = await client.resolve_peer('username')
seems like the problem is caused because I am resolving peer by getting full user by his username instead of just getting it by user_id and access_hash, however, after checking .session file I noticed that there is no peers stored at all. I opened it as SQLite database and opened peers table. It is completely empty.
Is it problem on my side or am I doing anything wrong? Why pyrogram does not cache user_id, access_hash and other fields so I could just get user from cache instead of resolving user by username every time
Steps to reproduce
Call .resolve_peer('username') method a few times
Code example
No response
Logs
No response
The text was updated successfully, but these errors were encountered:
Checklist
pip3 install -U https://github.com/pyrogram/pyrogram/archive/master.zip
and reproduced the issue using the latest development versionDescription
Telegram says: [420 FLOOD_WAIT_X] - A wait of 78 seconds is required (caused by "contacts.ResolveUsername")
here is my code that causes the error
seems like the problem is caused because I am resolving peer by getting full user by his username instead of just getting it by user_id and access_hash, however, after checking .session file I noticed that there is no peers stored at all. I opened it as SQLite database and opened peers table. It is completely empty.
Is it problem on my side or am I doing anything wrong? Why pyrogram does not cache user_id, access_hash and other fields so I could just get user from cache instead of resolving user by username every time
Steps to reproduce
Code example
No response
Logs
No response
The text was updated successfully, but these errors were encountered: