Playlist creation of any kind fails SILENTLY if the playlist directory does not exist
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
Any attempt to create a playlist in RetroArch, using any front end, will silently fail if the specified playlist destination directory does not currently exist.
Expected behavior
EITHER:
- The specified directory is auto-created and the playlist is added,
- OR RetroArch indicates to the user that playlist creation failed because the directory is not there
- OR, at absolute minimum, RetroArch indicates that playlist creation somehow failed without going into specifics.
Actual behavior
Playlist creation steps are allowed to continue and complete as though there are no problems and no errors are displayed, but no playlists are added.
Steps to reproduce the bug
- Get a new installation of RetroArch; download the databases, a ROM or two, and an accompanying core.
- Change the "playlist" directory to a new directory path that does not presently exist.
- Attempt to add a playlist by scanning the directory with your ROM(s) in it.
- Be mystified when there is no playlist and yet there was no indication that anything went wrong.
Version/Commit
- RetroArch: 1.9.0; Git Version 6388872a54
Environment information
- OS: Windows 10 20H2
Contributor guide
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.
Research direction
No file, test, or entry point is named in the issue. Reproduce the scan with a playlist directory that does not exist, then trace playlist creation from that action; the work is done when the directory is created or the failure is reported instead of appearing successful.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100