-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
BadFiles Crashing at launch #3165
Comments
Hi! Could you please follow the issue template so we can see your platform setup, etc.? That stuff will actually be really important for understanding this problem. It looks like the badfiles plugin is using the filesystem encoding to decode a program's output stream, which is clearly wrong. We should also probably be ignoring or replacing errors for this decode call, but it will take some careful consideration to see if that's safe. |
I apologize. Where can I find this template? I've searched and can not find it. |
It's what appears when you try to file a new issue in this repository. You can hit the "new issue" button and copy it out of there. Or get it here: |
ProblemI'm still new to Beets and am trying to perfect my setup. I'm up to Badfiles and am getting the following error when running "beet bad". Any help would be appreciated.
Running this command in verbose ( beet bad -vv Led to this problem:
Setup
My configuration (output of
|
Thanks! I've pushed a possible fix. Can you please verify that this fixes the error for you? |
I tried to pip upgrade and its stating that I am up to date pip install -U beets Requirement already up-to-date: beets in c:\users\bryan\appdata\local\programs\python\python36\lib\site-packages (1.4.8) |
You will need to run from source (see the FAQ). |
alright, Its been running for about 20 minutes now with no issues. Looks
fixed. thank you
…On Sun, Feb 24, 2019 at 5:18 PM Adrian Sampson ***@***.***> wrote:
You will need to run from source (see the FAQ).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3165 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Aid1H_2yEMTeQ2gp8xr8uY0L3YHtSQ-lks5vQw_FgaJpZM4bOi3T>
.
--
Thanks,
BryanGauvin
|
Excellent; thanks for checking! |
Hello,
I'm still new to Beets and am trying to perfect my setup. I'm up to Badfiles and am getting the following error when running "beet bad". Any help would be appreciated.
�[31;01m\ABRP\New Volume\Music-Flac\2Pac\All Eyez on Me\04 - Got My Mind Made Up feat. Delmar Arnaud, Kurupt, Redman & Method Man.mp3�[39;49;00m: file does not exist
Traceback (most recent call last):
File "C:\Users\Bryan\AppData\Local\Programs\Python\Python36\Scripts\beet-script.py", line 11, in
load_entry_point('beets==1.4.7', 'console_scripts', 'beet')()
File "c:\users\bryan\appdata\local\programs\python\python36\lib\site-packages\beets\ui_init_.py", line 1256, in main
raw_main(args)
File "c:\users\bryan\appdata\local\programs\python\python36\lib\site-packages\beets\ui_init.py", line 1243, in _raw_main
subcommand.func(lib, suboptions, subargs)
File "c:\users\bryan\appdata\local\programs\python\python36\lib\site-packages\beetsplug\badfiles.py", line 119, in check_bad
status, errors, output = checker(path)
File "c:\users\bryan\appdata\local\programs\python\python36\lib\site-packages\beetsplug\badfiles.py", line 81, in checker
return self.run_command(cmd)
File "c:\users\bryan\appdata\local\programs\python\python36\lib\site-packages\beetsplug\badfiles.py", line 64, in run_command
output = output.decode(sys.getfilesystemencoding())
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x92 in position 25: invalid start byte
The text was updated successfully, but these errors were encountered: