2 ms·

I went to do some testing in a sandbox system (as the compilation strategy is unclear, missing builds for some of the artifacts). I was able to initially const

by raggi 3y ago

I went to do some testing in a sandbox system (as the compilation strategy is unclear, missing builds for some of the artifacts). I was able to initially construct an archive of the linux tree (that failed in decompression), but subsequently went to rebuild it and the tool is repeatedly producing this output even in an otherwise cleaned up environment: Runtime error 203 at $0000000100009B72 $0000000100009B72 $00000001000225B6 $0000000100023153 $000000010002319A Runtime error 203 at $0000000100009B72 $0000000100009B72 $00000001000225B6 $0000000100023153 $000000010002319A Runtime error 203 at $0000000100009B72 $0000000100009B72 $00000001000225B6 $0000000100023153 $000000010002319A Runtime error 203 at $0000000100009B72 $0000000100009B72 $00000001000225B6 $0000000100023153 $000000010002319A Runtime error 203 at $0000000100009B72 $0000000100009B72 $00000001000225B6 $0000000100023153 $000000010002319A The first output did work, sadly I deleted it. It was over 400mb, so approximately double the size of a zip or a tar.zst of the same files. zstd natively compresses a tar of this set to 209mb in 800ms in multi-threaded mode, or 3.5s in single threaded mode. I suspect that sqlite is being held incorrectly (access from multiple threads, with multi-threading disabled), and the vfs lock forwarding is broken on Windows.

OttoCoddo 3y ago
Did you compile it for yourself? Any problem or steps you used, I will be happy to hear, o at pack.ac or GitHub, as it is hard to follow the building here. I should prepare more documents on how to build it. I suspect that there is a problem with the custom build. Error and speed issues are not something you see in the official build.
- raggi 3y ago
  That was the binary download from the website. You have a build.sh for the Linux binary artifacts, but no equivalent for the windows artifacts so i did not bother preparing a windows build
  - OttoCoddo 3y ago
    Pack binary? Can you tell what machine and what steps? Build.sh can be used for Windows too, using MSYS2 UCRT64.
    - raggi 3y ago
      Windows 11 sandbox, running atop Windows 11. Binary downloaded from your webpage. Data being packed was an unzipped copy of linux-master.zip fetched from GitHub unpacked with windows zip, selecting skip for the overlapping case files.
      - OttoCoddo 3y ago
        What are the parameters you gave to the CLI program? This issue seems interesting, as these files on Windows 11 were tested countless times. To be clear, you can run Pack as: `pack.exe ./linux-master/`
        raggi 3y ago
        I ran pack that way, and observed the error I posted

by raggi 3y ago

OttoCoddo 3y ago

Did you compile it for yourself? Any problem or steps you used, I will be happy to hear, o at pack.ac or GitHub, as it is hard to follow the building here. I should prepare more documents on how to build it. I suspect that there is a problem with the custom build. Error and speed issues are not something you see in the official build.

raggi 3y ago
That was the binary download from the website. You have a build.sh for the Linux binary artifacts, but no equivalent for the windows artifacts so i did not bother preparing a windows build
- OttoCoddo 3y ago
  Pack binary? Can you tell what machine and what steps? Build.sh can be used for Windows too, using MSYS2 UCRT64.
  - raggi 3y ago
    Windows 11 sandbox, running atop Windows 11. Binary downloaded from your webpage. Data being packed was an unzipped copy of linux-master.zip fetched from GitHub unpacked with windows zip, selecting skip for the overlapping case files.
    - OttoCoddo 3y ago
      What are the parameters you gave to the CLI program? This issue seems interesting, as these files on Windows 11 were tested countless times. To be clear, you can run Pack as: `pack.exe ./linux-master/`
      - raggi 3y ago
        I ran pack that way, and observed the error I posted