Issues

core: CompressionError absorbs three unrelated error types into Failed(String), with no source
otsobide/collapse#107 · opened on Aug 27, 2026
desktop: the host-rules path is never exercised on Windows, which is where it matters
otsobide/collapse#94 · opened on Aug 26, 2026
core: Windows users see the \\?\ verbatim prefix in every per-entry error message
otsobide/collapse#92 · opened on Aug 26, 2026
release: the guard checks two of the eight version strings, and bumping the rest is manual
otsobide/collapse#77 · opened on Aug 22, 2026
core: zip and 7z hold whole files in memory, on compression as well as extraction
otsobide/collapse#76 · opened on Aug 22, 2026
ci: nothing builds the container images, and one of them was broken for a while
otsobide/collapse#74 · opened on Aug 22, 2026
server-backend: no extraction endpoint, so the web app can only compress
otsobide/collapse#73 · opened on Aug 22, 2026
server-backend: no authentication, no rate limiting, no TLS, which is why everything is published on loopback
otsobide/collapse#72 · opened on Aug 22, 2026
remote: the poll loop has no upper bound, so a stuck job hangs the caller forever
otsobide/collapse#71 · opened on Aug 22, 2026
1
desktop: run() and the app wiring are verified only by the compiler
otsobide/collapse#69 · opened on Aug 22, 2026
desktop: the IPC boundary is modelled by a parser, never driven by the real one
otsobide/collapse#68 · opened on Aug 22, 2026
core: extraction has no guard against overwriting anything
otsobide/collapse#62 · opened on Aug 22, 2026
1
core: guard extraction against decompression bombs (size/ratio/count limits)
otsobide/collapse#7 · opened on Aug 14, 2026 · MVP: CLI + Desktop