zipfile | extract infos from zip file in javascript | Runtime Evironment library

The error basically says your string is byte string. To solve this, I think you can try to use .decode('utf-8')

383 on the log is not the batch size. It's the number of steps which is data_size / batch_size.

The problem that training does not work properly is probably because of very low or high learning rate. Try adjusting the learning rate.

Indeed, you code compresses local files to local ZIP archive. Note how your code never uses the sftp variable.

If you want to compress remote files to remote ZIP archive using a local Python script, you have to download the remote files, zip them locally and upload the ZIP archive.

You can do that all that "in-memory" without actually storing the remote files or the ZIP file physically to the local system. But you still need to do all the transfers. So it will be terribly inefficient.

You better execute zip command on the remote server using your SFTP (or SSH actually) connection.

Related question: How to decode Zip file from sftp file using paramiko python

The first argument of send_bytes should be a function handle that writes content to BytesIO. Adopting your example, the code would be

Instead of using put_file, you can use create_commit which takes multiple files in its putFiles parameter. I was able to do it using this code-

I suggest you use this

app.root_path contains the root path for the application. This is determined based on the name passed to Flask. Typically, you should use the instance path (app.instance_path) not the root path, as the instance path will not be within the package code.

Like most Python classes, this one requires you to create an instance, then use its methods.

Unfortunately the zip crate requires a self-referential struct for such usage. Self-referential structs are not allowed by the borrow checker, but you can avoid the underlying problem by heap-allocating ZipArchive to prevent it from moving.

Even with the use of Box for heap allocation, the borrow checker still won't accept the resulting code because it doesn't special-case Box, and because it can't prove that some code won't move the object out of the box. To make it compile you'll need to use unsafe transmute to decouple the borrow of ZipFile from the archive. It will be up to you to maintain the invariants: that ZipArchive doesn't move and that ZipFile gets destroyed before ZipArchive. Fortunately the code is short, so it should be easy to review for correctness.

Here is a possible implementation:

Both of these errors indicate that the specified file is not a valid zip archive. So I expect something is going wrong with the writing of the file (by the step prior to find-and-replace).

I would start by stopping the process after writing the file and seeing if the file is present on the filesystem and whether it can be opened manually using Word. This should bisect the problem and narrow it down to a writing problem or a reading problem.

It could be possible that an error is raised on the write and it's not being caught or whatever, leaving an empty or un-flushed (open) file. So having a way to monitor that step is probably a good idea. Writing to a log comes to mind as how you might manage that.

Inspecting the particular cases where there is a failure and managing to reproduce it are going to be critically important. If that's not possible, it's going to be a tough road of guesswork and disappointment on both sides.