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
Describe the bug
Excludarr is not properly parsing environment variables that have the character ! in their values. There's no error message, but the whole variable is ignored (when specifying multiple TV series to exclude, all of them are non-ignored, just not the one with !).
That is strange, have you tried it with double quotes as well? SONARR_EXCLUDE="Cowboy Bebop, Call My Agent!". I am developing a new version with a UI right now, in this version the exclude list will be filled in a form, hence formatting it correctly by default.
My original trial was with double quotes actually. I tried single quotes to see if this was not an interaction with the shell's parsing of !, but it does not change anything. I also tried \!, no luck...
Hmpf bummer, I am not fixing anything in version 1 of excludarr anymore. This will be fixed in version 2 of excludarr. I am hoping to release around the end of this year.
Describe the bug
Excludarr is not properly parsing environment variables that have the character
!
in their values. There's no error message, but the whole variable is ignored (when specifying multiple TV series to exclude, all of them are non-ignored, just not the one with!
).To Reproduce
Steps to reproduce the behavior:
docker run -it --rm --env-file excludarr.env haijeploeg/excludarr:latest sonarr exclude --action delete --progress
Call My Agent!
excludarr.env
file:SONARR_EXCLUDE='Cowboy Bebop, Call My Agent!'
Expected behavior
I would expect both Cowboy Bebop and Call My Agent! to be ignored.
Versions
I'm using the
latest
Docker tag as of 2022-11-26.Debug logging
Running in debug mode shows the configuration that's created from the command-line + env. variables:
Looking at the content of the
exclude
entry in the dictionary, it looks like the env. variable was not properly split.The text was updated successfully, but these errors were encountered: