Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Upgrading to Beta 12 makes smart file skipping missbehave in previously watched folders

Open
#685 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
visualbasic
Domain
desktop

Research direction

Reproduce the regression by upgrading to Beta 12, updating files in a previously watched folder, and running the watched-folder analyze-compress routine. Inspect how the smart file skipper populates the exclusions list shown through Home > Compress again > Exclusions > Edit list. Done means highly compressible files such as .ucas are no longer incorrectly skipped in previously watched folders.

Written by the indexing model from the issue text.

Description

Description

Upgrading to Beta 12 makes smart file skipper missbehave in previously watched folders.
My case is The FINALS with highly compressible .ucas files being marked by the smart file skipper.
Tested several times, the issue was resolved when i removed the game from the watched folder list.

Reproduce

  • Upgrade compactgui to beta 12
  • Update a watched folder files (in this case The Finals update) so some files get decompressed
  • Run the watched analyze-compress routine.
  • Notice way lower compression than before. To see what happened:
    • In home tab - compress again - exclussions - edit list. Notice that smart skipped files are added. In this case .ucas that are big and highly compressible
Dominant language
Visual Basic .NET
Stars
8.9k
Forks
343
Avg merge
3d 18h
Merged PRs (30d)
7

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IridiumIO/CompactGUI

All issues in IridiumIO/CompactGUI

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.