archiver | Easily create & extract archives | Compression library

The problem is that you are not being able to zip your files properly, this can occurs by many issues, including:

• You are not waiting the file to be processed, you need to use .close() event to do this.
• You are not sending the correct path to the files or dirs to zipped, normally the files that you upload together with the lambda files on the root dir of your project stay on /var/task/ on the Lambda dir system, so to send the correct file use __dirname + '/file.name'
• You are not appending correctly the files, check the .file() and .append() methods if you are sending the files correctly

If you have the following Lambda structure:

As can be seen in the comments of the post, my problem is fixed, so I thought I'd collect a closing answer here to not leave the post pending.

The actual solution: As explained here nicely by @UninformedUser, the issue was that I had conflicting maven package versions in my dependencies. Bringing everything in sync with each other solved the issue.

Incidental solution: As I wrote in the comments above, specifically defining 3.3.0 for the maven-assembly-plugin happened to solve the issue. But this was only chance, as explained here by @Ignazio, just because the order of "assembling" things changed, overwriting the conflicting package.

Huge thanks to both for the help.

I just solve this issue by correcting the RxJS version to 7.4.0. I hope this can solve others issue as well.

This seems to be some File system error more than maven issue, check if your disk has enough space to / you have the correct permissions to complete the build. Usually when I am building ranger this works for me the fastest and best.

This is not something weird pgadmin does, but rather it is something weird Windows itself does when needing to represent such file names in a DOS-like setting. Like when the name is more than 8 chars, or extension more than 3.

In my hands the weird presentation is only there in the logs and status messages. If I use the GUI file chooser, the file names look normal, and replay successfully.

If you really want to know what Windows is doing, I think that is a better question for superuser with a Windows tag. I don't know why you can't restore these files. Are you using the pgAdmin GUI file chooser or trying to type the names in directly to something?

Does it make sense to iterate through layers like this and keep adding files (to some target, does not matter for now) and deleting the added files in case they are found with a .wh prefix? Or am I totally off and is there a much better way?

There is a much better way, you do not want to reimplement (with worse performances) what Docker already does. The main reason is that Docker uses a mount filesystem called overlay2 by default that allows the creation of images and containers leveraging the concepts of a Union Filesystem: lowerdir, upperdir, workdir and mergeddir.

What you might not expect is that you can reproduce an image or container building process using the mount command available in almost any Unix-like machine.

I found a very interesting article that explains how the overlay storage system works and how Docker internally uses it, I highly recommend the reading.

Actually, if you have read the article, the solution is there: you can mount the image data you have by docker inspecting its LowerDir, UpperDir, WorkDir and by setting the merged dir to a custom path. To make the process simpler, you can run a script like:

One possibility is that the serverless sagemaker version is trying to write the model in the same place that you have already wrote it in your inference container.

Maybe review your custom inference code and don't load the model there.

A piece as it says about a zip archive in the error. There is no actual stream assigned with the place e,g, you have a String path but analogous there is not actually so much as an actual .io.File related part of the code. There is however a constructor for such document that takes a Stream argument on construction.

Your version of Java is incompatible with your version of NetBeans because NetBeans 12.2 does not support the use of JDK 17. From the NetBeans 12.2 Release notes Downloading Apache NetBeans 12.2:

Apache NetBeans 12.2 runs on JDK LTS releases 8 and 11, as well as on JDK 15, i.e., the current JDK release at the time of this NetBeans release.

In general, when changing your version of NetBeans and/or Java, make sure that the versions are compatible. This is always documented in the NetBeans release notes.

You have two options to resolve this:

• Upgrade to NetBeans 12.6 which supports Java 17.
• Stay on NetBeans 12.2, but downgrade to Java 15 or lower. That is, make JDK 15 (or lower) your default platform for NetBeans 12.2.

Of course you may also have other issues with your project, but there is no point in worrying about those until you have fixed this problem.