Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: No such file or directory (os error 2) #8

Open
Visne opened this issue Jul 30, 2023 · 7 comments
Open

Error: No such file or directory (os error 2) #8

Visne opened this issue Jul 30, 2023 · 7 comments
Labels
bug Something isn't working

Comments

@Visne
Copy link

Visne commented Jul 30, 2023

This often happens after "Transcoding..." is printed. I'm not sure why it happens.

@Visne
Copy link
Author

Visne commented Jul 30, 2023

I'm pretty sure it happens when the torrent has a forward slash in the name, because then it is interpreted as a directory in a directory.

@DevYukine
Copy link
Owner

I'm pretty sure it happens when the torrent has a forward slash in the name, because then it is interpreted as a directory in a directory.

That could be, i didn't try out what happened to paths when i have a slash in the name, i'll investigate this

@DevYukine DevYukine added the bug Something isn't working label Jan 16, 2024
@DC-Melo
Copy link

DC-Melo commented Apr 17, 2024

great

@noeRls
Copy link
Contributor

noeRls commented Jun 8, 2024

+1

@noeRls
Copy link
Contributor

noeRls commented Jun 8, 2024

I opened a PR that fix this issue.

If you want a fix right now, you just need to make sure that your transcode directory exist.

@punowo
Copy link

punowo commented Dec 9, 2024

No matter what I do I encounter this error on both the latest version of Mac OS and Arch. I've tried multiple torrents with no special characters in the artist or album name.

[❌] Skipping due to encountered error: No such file or directory (os error 2)
{
	"api_key": "",
	"torrent_directory": "/home/punowo/Oxide/torrent",
	"content_directory": "/home/punowo/Oxide/content",
	"transcode_directory": "/home/punowo/Oxide/transcode",
	"spectrogram_directory": "/home/punowo/Oxide/spectrogram",
	"move_transcode_to_content": false,
	"automatic_upload": false,
	"skip_hash_check": false,
	"skip_spectrogram": false,
	"allowed_transcode_formats": ["Mp3320", "Mp3V0"],
	"concurrency": 16
}

On Mac, the full paths started with /Users/..I also tried "~". I know zero rust but please panic accordingly with a stacktrace instead of just this error. The folders specified, have already been created.

@punowo
Copy link

punowo commented Dec 10, 2024

I do believe some people are encountering this for other reasons. As someone who's never used BetterRed I looked a little at the dependencies and it seems there's nothing really there that's actually used to download the torrents so when I pass a PL to red_oxide that torrent should already be downloaded somewhere right ? Or maybe I'm the only one encountering it.

EDIT: Yeah it was just me because I didn't understand how to properly use the tool. The content directory needs the source of the transcode to be already there when red_oxide is ran.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants