put_object_stream_blocking uploads 0B file about rust-s3 HOT 5 CLOSED

My workaround for now is to read the whole file into memory and use put_object_blocking. Not ideal but I'm not working with big files.

      // Open the file
      let mut file = File::open(path).expect("Unable to open file!");

      let mut buffer = Vec::new();
      // read the whole file
      file
        .read_to_end(&mut buffer)
        .expect("Unable to read to end");

      // Upload file to AWS
      let (_, status_code) = bucket
        .put_object_blocking(&server_filename, &buffer, "application/octet-stream")
        .unwrap_or_else(|e| {
          error!("Unable to upload {}! Error: {}", &server_filename, e);
          std::process::exit(1);
        });

from rust-s3.

@jaredwolff thank you for raising the issue, I'll look into it ASAP

from rust-s3.

I came into the same issue too.
The put_object_stream_blocking just uploaded an empty file, discarding the content.

from rust-s3.

@jaredwolff, @jiangplus version 0.23 released today fixes this

from rust-s3.

This is very likely not the same issue but I had a problem with the same result. Problem was I needed to reset the pointer for the file with file.seek(SeekFrom::Start(0)).await?; before uploading.

from rust-s3.