-
Notifications
You must be signed in to change notification settings - Fork 386
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
[Bug]: Invalid cover path crashes container #2007
Comments
The error log isn't giving us anything useful to go off of. I just tested putting in a bad path, putting in a good path, and putting in a URL to an image. All of those worked properly. When putting in a path that doesn't exist the server shows this error:
Can you give more specific details on how to reproduce this error? |
Sure thing. Specifically, a path ending in a directory with a Hitting save at this point will cause a socket disconnect. I just recreated this to get double check, and the container managed to recover, which is not what I observed 2 weeks ago. I have not changed versions in that time, so perhaps I just wasn't patient enough with the container before or my server was just having an off day, in which case this can be closed. For what its worth, I did some digging in the repo and I believe it's coming from this method in fileUtils when called from this method in CoverManager. I've never been much of a JS guy, much less using the larger frameworks, so apologies if that's not a particularly helpful suggestion. |
I was able to reproduce this. It is specific to entering a file path that exists but is not a file. I fixed it by checking that the path is a file and not a directory. |
Fixed in v2.4.0 |
Describe the issue
Editing the cover path to a directory causes the container to crash. Visually, the web app just shows the socket connection failed. I have also tested this with non-image files and files that do not exist, both of these cases are handled correctly. Logs attached.
audiobookshelf-logs.txt
Edit: Debug logs
audiobookshelf-debug-logs.txt
Steps to reproduce the issue
Audiobookshelf version
2.3.3
How are you running audiobookshelf?
Docker
The text was updated successfully, but these errors were encountered: