Prevent "untracked files" situation by altering `.smm` marker file handling
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- tooling
Research direction
Locate the code that creates and deletes .smm marker files, along with the mod extraction and uninstall entry points. Trace the failure paths around extraction and deletion; done means interrupted cleanup cannot make a folder appear unmanaged, and the marker lifecycle matches the behavior described in the issue.
Written by the indexing model from the issue text.
Description
If the mod manager encounters a problem while deleting mod files, it could end up leaving some of them behind but still delete the .smm marker file, making it think the folder is an unmanaged mod, leaving behind files that need to be cleaned up manually.
I think I've seen the untracked files issue before, and the solution is to have the
.smmmarker file be created before extracting any files, but be empty, then the hash written to it after the extraction is complete, and when uninstalling, it should be the last file deleted (i.e. delete all the contents of the folder first, except for that file, then delete the folder)
https://discord.com/channels/555424930502541343/1193986432574963782/1497328490167402576
- Dominant language
- Svelte
- Stars
- 502
- Forks
- 94
- PR merge metrics
- No merged PRs in 30d
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from satisfactorymodding/SatisfactoryModManager
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
satisfactorymodding/SatisfactoryModManager#363 · 1 comment ·
-
SMM 3.1.0 Satisfactory Steam Stable 1.2 Actual build CL495413 Resolver incorrectly uses CL273254Open
Difficulty 3/5 1-2 days Newbie friendliness 58/100
satisfactorymodding/SatisfactoryModManager#361 · 1 comment ·
-
Custom game pathOpen
Difficulty 3/5 1-2 days Newbie friendliness 55/100
satisfactorymodding/SatisfactoryModManager#360 · 1 comment · 1 reaction ·
All issues in satisfactorymodding/SatisfactoryModManager
Similar issues
-
skillfs: one malformed chat-log line aborts the entire skill-usage analysis (skill_usage_from_chat_logs.py)Possibly taken @zjncs claimed this today. Opencomponent:skillfs
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
agentic-os-org/ANOLISA#6116 · 1 comment ·
Maintainers usually reply within 1 day
-
kwok: shared-cluster runs leak kube-system releases between recipes, failing inventory read-backOpenarea/tests theme/ci-dx
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
FluidNumerics/fluid-walk-blocker#172 ·
Maintainers usually reply within 1 day
-
Forge coverage prompts carry text the agent cannot act onPossibly taken @graalvmbot claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
oracle/graalvm-reachability-metadata#10572 ·
Maintainers usually reply within 1 day