Tranquil IT Forum

Hello,

since the update we've been encountering this error when editing packages, and we no longer see the local repository in the console.
Before uploading to the server, we had a section in the console to edit a package; now we no longer have the "

Windows Environment version 3505"

Geoffroy wrote: ↑Feb 15, 2023 - 12:04 PM Hello,

Since the update, we've been encountering this error when editing packages, and we no longer see the local repository in the console.
Before uploading to the server, we had a section in the console to edit a package; we no longer have the "

Windows Environment version 3505"

exact version 3505 -> 2.3.0.13505? Enterprise/Discovery?

For the package editing tab integrated into the console, you need to check "show developer features" in the view/preferences menu.

Are you experiencing this problem only with this software, or with other .exe files as well? What is the size of the .exe file?

Denis

Hello,

Thank you for your initial response; that's exactly what I wanted.

Regarding the other issue, it occurs with all large packages under 2GB.


We are using Windows Server 2019 for the server and Windows 10 version 2.3.0.13505 for the console (Enterprise edition).

Thank you for your feedback.

Hello,

following debugging with Geoffroy, there is indeed an issue with some large packages. The problem seems to stem from a compatibility issue with a file that was generated in zip64 format using Python (which was used in version 2.2 to generate WAPT packages), and then reopened using FPC/Lazarus (the console language, which is now also used in version 2.3 for generating WAPT packages). We are currently looking into how to address this issue.

If you need to make a change quickly, a workaround is to download the WAPT file using a browser and unzip it with 7-Zip (which is more tolerant of the format), then re-import the unzipped package directory into the console.*

Sincerely,

Denis