Lonami Exo 987cf41ec6 Higher timeout and log them as warning if any data was received ...

This might be the cause for  "number of retries reached 0" so
more specific logging calls might be useful. If while reading
a response it times out but  some data had already been read,
said data will be lost.

The sequence of events that triggered reaching 0 retries was:
- Sending requests with IDs XYZ
- socket.timeout while reading
- Items timed out. Retrying
- Processing RPC result
- Received response for XYZ
- Lost request with ID XYZ

2018-03-18 20:08:00 +01:00

..

crypto

Dump libssl bindings in favour of the new optional cryptg module

2018-02-16 18:24:44 +01:00

errors

Errors: Fix passing 'self' to the constructors of the superclasses

2018-02-14 17:09:22 +10:00

events

Fix assignement to wrong variable on ChatAction

2018-03-18 10:24:48 +01:00

extensions

Higher timeout and log them as warning if any data was received

2018-03-18 20:08:00 +01:00

network

Add more logging calls when confirming a request

2018-03-07 11:30:03 +01:00

sessions

Remove SQLAlchemy session

2018-03-17 17:38:16 +01:00

tl

Rename and reorder some params in Draft for consistency (#673)

2018-03-08 13:05:40 +01:00

__init__.py

Use NullHandler as default for the library

2017-11-13 10:59:43 +01:00

helpers.py

Move utils.calc_msg_key into auth_key (cyclic imports py3.4)

2018-01-08 12:07:14 +01:00

telegram_bare_client.py

Bring back report_errors to the constructor

2018-03-15 10:22:21 +01:00

telegram_client.py

Higher timeout and log them as warning if any data was received

2018-03-18 20:08:00 +01:00

update_state.py

Stopping workers should not clear their count (may fix #686)

2018-03-15 10:30:05 +01:00

utils.py

Stop sending gifs as images

2018-03-15 10:13:57 +01:00

version.py

Update to v0.18.1

2018-03-17 17:38:46 +01:00