add example for file upload with progress

[xinst]

I added a simple way to track the upload progress, a little trick only

[jasdel]

Thanks for creating this example @xinst

[ibrt]

@xinst FYI the example is broken... What happens is that the uploader reads the whole thing twice, haven't dug into why but I think it has to do with determining the number of parts. The first read is very fast as the contents are discarded. The second actually seems to be piped to the upload.

The sample reports progress by dividing the number of bytes read by two, so what I'm seeing is that it jumps straight to 50%, and then proceeds to 100% at half the actual "speed". I "fixed" it by initializing read to -size, starting to report when read passes 0.

[jasdel]

Thanks for the feedback, @ibrt would you mind creating a Github issue for this bug? I think we should update the original upload progress example to use similar output as the new download progress PR, #2456

[xinst]

Thanks for the feedback, @ibrt would you mind creating a Github issue for this bug? I think we should update the original upload progress example to use similar output as the new download progress PR, #2456

that's awesome could display a progress bar in the sample

[xinst]

@xinst FYI the example is broken... What happens is that the uploader reads the whole thing twice, haven't dug into why but I think it has to do with determining the number of parts. The first read is very fast as the contents are discarded. The second actually seems to be piped to the upload.

The sample reports progress by dividing the number of bytes read by two, so what I'm seeing is that it jumps straight to 50%, and then proceeds to 100% at half the actual "speed". I "fixed" it by initializing read to -size, starting to report when read passes 0.

I was test with some small(less than 5MB) and large files when I wrote this sample, it was worked for me at that time when divided by two, it was strange. I didn't met the progress straight jumps to 50%.

[anacrolix]

This is an unsound example: It abuses the knowledge that the input is read twice, and should be named putObjectWithProgress, not Process.