[BUG] Steam scan fails for DrinkBox_Game4 (Guacamelee! Super Turbo Championship Edition)
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
Research direction
Start by reproducing the Steam scan failure with the DrinkBox_Game4 symlink pointing to the Guacamelee folder, and inspect how the scan resolves folder names against the database entry. The report also says scanning stops at the first error; check whether that behavior is part of the same failure. Done means the named game scans successfully and the result for subsequent items is clear.
Written by the indexing model from the issue text.
Description
This error does not seem to appear in the log files.
Note that DrinkBox_Game4 is a hidden symlink to a Guacamelee folder, which seems likely related.
(The reasoning being steam works with the DrinkBox_Game4 folder name but it bothered me that it didn't use the actual game name).
I would understand a failed scan for the Guacamelee folder but it should succeed for the DrinkBox_Game4 folder, as the DB has "FolderName": "DrinkBox_Game4".
A loosely related issue is that it seems that scan stops at the first error, instead of continuing to scan the rest of items.
Found on Version 4.0 Beta 12.
- 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
- 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 IridiumIO/CompactGUI
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
IridiumIO/CompactGUI#699 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
IridiumIO/CompactGUI#697 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
IridiumIO/CompactGUI#696 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
IridiumIO/CompactGUI#680 ·
Maintainers usually reply within 3 days
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
IridiumIO/CompactGUI#698 ·
Maintainers usually reply within 3 days
All issues in IridiumIO/CompactGUI
Similar issues
-
good first issue help wanted r-feature
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
servo/rust-smallvec#792 ·
Maintainers usually reply within 1 day
-
updater
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
UniversityOfHelsinkiCS/oodikone#5141 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
praetorianer777/Dynamo#53 ·
Maintainers usually reply within 1 day
-
feature-request
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
stripe/stripe-dotnet#3484 ·
Maintainers usually reply within 2 days
-
[Bug] Parameters named like a property break to_xcal()Possibly taken @atharvasalunke1267 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
collective/icalendar#2018 · 2 comments ·
Maintainers usually reply within 1 day