Hi,
On Mon, Nov 14, 2016 at 12:33:46PM -0600, Jonathon Jongsma wrote:
> hmm, you're right. But it's a little bit weird that we don't flush this
> message but we do all other file-transfer messages. That means that for
> zero-length files we'll never receive GError reports for failed
> sending/flus
On Fri, 2016-11-11 at 23:53 +0100, Victor Toso wrote:
> Hi,
>
> On Fri, Nov 11, 2016 at 04:05:21PM -0600, Jonathon Jongsma wrote:
> >
> > On Fri, 2016-11-11 at 14:27 +0100, Victor Toso wrote:
> > >
> > > From: Victor Toso
> > >
> > > This fixes the situation when VDAgent receives 0 byte messag
Hi,
On Fri, Nov 11, 2016 at 04:05:21PM -0600, Jonathon Jongsma wrote:
> On Fri, 2016-11-11 at 14:27 +0100, Victor Toso wrote:
> > From: Victor Toso
> >
> > This fixes the situation when VDAgent receives 0 byte message
> > regarding a file-transfer operation that was terminated in the
> > previou
On Fri, 2016-11-11 at 14:27 +0100, Victor Toso wrote:
> From: Victor Toso
>
> This fixes the situation when VDAgent receives 0 byte message
> regarding a file-transfer operation that was terminated in the
> previous message.
>
> This makes the VDAgent to send a STATUS_ERROR after STATUS_SUCCESS
From: Victor Toso
This fixes the situation when VDAgent receives 0 byte message
regarding a file-transfer operation that was terminated in the
previous message.
This makes the VDAgent to send a STATUS_ERROR after STATUS_SUCCESS to
client.
Resolves: https://bugs.freedesktop.org/show_bug.cgi?id=9
