mirror of
https://github.com/pyrogram/pyrogram
synced 2025-08-30 13:57:54 +00:00
Update FAQ
This commit is contained in:
parent
cb5431d976
commit
371700ddec
@ -19,7 +19,7 @@ This FAQ page provides answers to common questions about Pyrogram and, to some e
|
|||||||
- :doc:`uploading-with-urls-gives-error-webpage-curl-failed`
|
- :doc:`uploading-with-urls-gives-error-webpage-curl-failed`
|
||||||
- :doc:`sqlite3-operationalerror-database-is-locked`
|
- :doc:`sqlite3-operationalerror-database-is-locked`
|
||||||
- :doc:`sqlite3-interfaceerror-error-binding-parameter`
|
- :doc:`sqlite3-interfaceerror-error-binding-parameter`
|
||||||
- :doc:`socket-send-raised-exception-oserror-timeouterror`
|
- :doc:`socket-send-oserror-timeouterror-connection-lost-reset`
|
||||||
- :doc:`how-to-avoid-flood-waits`
|
- :doc:`how-to-avoid-flood-waits`
|
||||||
- :doc:`the-account-has-been-limited-deactivated`
|
- :doc:`the-account-has-been-limited-deactivated`
|
||||||
|
|
||||||
@ -40,6 +40,6 @@ This FAQ page provides answers to common questions about Pyrogram and, to some e
|
|||||||
uploading-with-urls-gives-error-webpage-curl-failed
|
uploading-with-urls-gives-error-webpage-curl-failed
|
||||||
sqlite3-operationalerror-database-is-locked
|
sqlite3-operationalerror-database-is-locked
|
||||||
sqlite3-interfaceerror-error-binding-parameter
|
sqlite3-interfaceerror-error-binding-parameter
|
||||||
socket-send-raised-exception-oserror-timeouterror
|
socket-send-oserror-timeouterror-connection-lost-reset
|
||||||
how-to-avoid-flood-waits
|
how-to-avoid-flood-waits
|
||||||
the-account-has-been-limited-deactivated
|
the-account-has-been-limited-deactivated
|
@ -0,0 +1,12 @@
|
|||||||
|
socket.send(), OSError(), TimeoutError(), Connection lost/reset
|
||||||
|
===============================================================
|
||||||
|
|
||||||
|
If you get any of these errors chances are you ended up with a slow or inconsistent network connection.
|
||||||
|
Another reason could be because you are blocking the event loop for too long.
|
||||||
|
|
||||||
|
You can consider the following:
|
||||||
|
|
||||||
|
- Use Pyrogram asynchronously in its intended way.
|
||||||
|
- Use shorter non-asynchronous processing loops.
|
||||||
|
- Use ``asyncio.sleep()`` instead of ``time.sleep()``.
|
||||||
|
- Use a stable network connection.
|
@ -1,13 +0,0 @@
|
|||||||
socket.send() raised exception, OSError(), TimeoutError()
|
|
||||||
=========================================================
|
|
||||||
|
|
||||||
If you get this error chances are you or Telegram ended up with a slow or inconsistent network connection, which
|
|
||||||
triggers internal timeouts due to data not being sent/received in time. Another reason could be because you are blocking
|
|
||||||
the event loop for too long, most likely due to an improper use of non-asynchronous or threaded operations which may
|
|
||||||
lead to blocking code that prevents the event loop from running properly.
|
|
||||||
|
|
||||||
You can consider the following:
|
|
||||||
|
|
||||||
- Use Pyrogram asynchronously in its intended way.
|
|
||||||
- Use shorter non-asynchronous processing loops.
|
|
||||||
- Use ``asyncio.sleep()`` instead of ``time.sleep()``.
|
|
Loading…
x
Reference in New Issue
Block a user