Bogus first status callback

[dkocher]

The first callback on TransferStatusCallbackListener#statusCallback has set bytesTransfered set to the total length even when totalFilesTransferredSoFar is still 0.

[dkocher]

This issue is not resolved in 4.0.2.1-RELEASE.

[michael-conway]

Hey david I fixed a place I found on the put...can you narrow down the type
of callback this was an issue then?

On Thu, Apr 23, 2015 at 4:05 PM, David Kocher [email protected]
wrote:

This issue is not resolved in 4.0.2.1-RELEASE.

—
Reply to this email directly or view it on GitHub
#88 (comment).

[dkocher]

I see. Looks like it is fixed for PUT but still bogus for GET. (From DataTransferOperations#getOperation)

[michael-conway]

OK we'll push out a little dot release after we nail down all of the
cyberduck stuff and add that.

I want to focus on getting the performance up to snuff first.

Cheers!
MC

On 4/23/15 4:29 PM, David Kocher wrote:

I see. Looks like it is fixed for PUT but still bogus for GET. (From
|DataTransferOperations#getOperation|)

—
Reply to this email directly or view it on GitHub
#88 (comment).

[dkocher]

I suppose this is now fixed with f786632.

[michael-conway]

Yes think so but of course events overtook this afternoon. Will sew that
up and push to maven soon
On Apr 24, 2015 4:50 PM, "David Kocher" [email protected] wrote:

I suppose this is now fixed with f786632
f786632
.

—
Reply to this email directly or view it on GitHub
#88 (comment).