You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just tried to run a report for my MAME ROMs, and while it seems to scan for DATs and ROMs okay, when generating the report, I get the error in the title.
✓ Scanning for DATs ············ | 1 unique DAT found
✓ Scanning for ROMs ············ | 12,032 unique ROMs found
✓ Detecting ROM headers ········ | 12,032 ROMs processed
✓ MAME ························· | 6,355/43,920 games, 7/75 BIOSes, 6,355/43,920 retail releases fod
✎ Generating report ············ | ░░░░░░░░░░░░░░░░░░░░░░░░░
ERROR: TypeCannot read properties of undefined (reading 'getRomsWithFiles')
I'm pretty sure this is something I'm doing wrong, vs. an actual bug, but not sure what to do to get the report.
Expected behavior
The command executes without an error and I can access the report.
Highly likely this is a bug with the code, maybe with the new MAME code from v1.6.6. I might not get a chance to dig in depth this week, but I will soon!
Confirmed this behavior with the same progetto-SNAPS DAT.
emmercm
added
bug
A confirmed issues that needs fixing
and removed
potential-bug
A potential issue that needs confirmation and/or triage
labels
Jul 12, 2023
Paste the command
npx igir@latest report --dat /Users/michael/Downloads/MAME_Dats_256/DATs/MAME\ 0.256.dat --input /Users/michael/Documents/Emulator\ Data/MAME/roms
Describe the bug
I just tried to run a report for my MAME ROMs, and while it seems to scan for DATs and ROMs okay, when generating the report, I get the error in the title.
I'm pretty sure this is something I'm doing wrong, vs. an actual bug, but not sure what to do to get the report.
Expected behavior
The command executes without an error and I can access the report.
Debug logs
debug.txt
igir version
1.6.6
Node.js version
20.4.0
Operating system
macOS 13.4.1 (22F82)
Additional context
No response
The text was updated successfully, but these errors were encountered: