ESOCKETTIMEOUT during move operation

[pixtron]

Describe the bug

1.) User moves /a/a.txt to /b/b.txt
2.) During the sync operation client runs in ESOCKETTIMEOUT, but server got the request and silently processes it.
3.) As the request was not successfull from the client perspective, the client puts the operation into the error queue and tries later.
4.) Upon next sync client tries to execute the move action again, but server responds with "source node a.txt is already in the requested parent folder"
5.) Client reschedules the operation again, although it could forget about it.

See RM24458

Expected behavior

The client should not reschedule the operation after recieving the error "source node a.txt is already in the requested parent folder"

Environment

• desktop client version: v1.2.2