On Wed, Jan 10, 2024 at 09:59:07AM +0100, Bence Ferdinandy wrote:
On Thu Aug 17, 2023 at 14:45, Oswald Buddenhagen <oswald.buddenha...@gmx.de>
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.
i don't think that's necessary. it "just" requires me looking really
hard at the code. the culprit must be one of the last commits to
socket.c (git-bisect'ing it would not hurt). if someone else wants to
take a shot at analyzing it, that would be most welcome.
I started bisecting,
based on what i said, you could pass `src/socket.c` to bisect to
significantly cut down the iterations.
anyway, as i said in another thread:
you can try reverting 859b7dd7f and later ac3b5186b.
which will probably get you right to the culprit.
but it's a pain due to the config changes between the last release:
it's backwards-compatible; you just get some deprecation notices with
the newer version. so just use the old config.
I'm getting "Near side box X cannot be opened" on the latest release. I deleted
.local/state/isync/, I cleared ~/.mbsync, I also cleared everything from Path.
What am I not clearing?
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 first guess would be that the config is missing a Create
statement, which wasn't important until you deleted the local state.
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
