Hi all,
On Thu Aug 17, 2023 at 14:45, Oswald Buddenhagen
wrote:
> On Thu, Aug 17, 2023 at 07:59:09AM -0400, brittanderson--- via isync-devel
> wrote:
> >The error has reoccured. It is:
> >
> >Socket error: receive buffer full. Probably protocol error.
I also ran into this error with davmail.
On Wed, Jan 10, 2024 at 09:59:07AM +0100, Bence Ferdinandy wrote:
On Thu Aug 17, 2023 at 14:45, Oswald Buddenhagen
wrote:
On Thu, Aug 17, 2023 at 07:59:09AM -0400, brittanderson--- via isync-devel
wrote:
>The error has reoccured. It is:
>
>Socket error: receive buffer full. Probably protocol
On Wed Jan 10, 2024 at 12:22, Oswald Buddenhagen via isync-devel
wrote:
> this doesn't look like a data incompatibility, so clearing won't do
> anything useful.
> try running with -D to see whether it's doing something obviously
> stupid. the next level would be strace'ing it.
> anyway, my firs
Result of bisect:
859b7dd7f2dc5d8396488700e0ab35d207188ed9 is the first bad commit
commit 859b7dd7f2dc5d8396488700e0ab35d207188ed9
Author: Oswald Buddenhagen
Date: Thu Jun 9 13:32:16 2022 +0200
try to avoid extra syscalls when reading sockets
so far we shifted down the buffered data o
