GitLab

Ondřej Kuzník authored Nov 22, 2017 and Ondřej Kuzník committed Nov 17, 2020

In preparation for operation timeout events.

Ondřej Kuzník authored Jun 30, 2017 and Ondřej Kuzník committed Nov 17, 2020

When the pdu processing limit is hit, we still attempt to read another
PDU. If we succeed, the ber_get_next call in the read callback will
abort since a full PDU is already present.

Ondřej Kuzník authored Jun 27, 2017 and Ondřej Kuzník committed Nov 17, 2020

Stats now logs all operations, stats2 additionally intermediate messages
(search entries).

Ondřej Kuzník authored May 18, 2017 and Ondřej Kuzník committed Nov 17, 2020

We reset the connection pointer on a destruction attempt, avoid the
spurious asserts.

Ondřej Kuzník authored May 18, 2017 and Ondřej Kuzník committed Nov 17, 2020

Do not log when receiving the last bytes on a connection. Log failed
writes.

Ondřej Kuzník authored May 10, 2017 and Ondřej Kuzník committed Nov 17, 2020

This alone doesn't make the server do a round robin.

Ondřej Kuzník authored May 09, 2017 and Ondřej Kuzník committed Nov 17, 2020

There was still a race where the connection could be freed as the
operation was still being used.

Ondřej Kuzník authored May 09, 2017 and Ondřej Kuzník committed Nov 17, 2020

The connection might be ready to read (close) but if we can't destroy it
yet, we don't want the callback to trigger all the time or process new
data.