Closed scratchmex closed 6 months ago
Hi there, thank you for the bug report, and I apologise for the late reply (I was on break for a while).
Looking at the logs, it's clear that Buildarr thinks the remote path mapping does not exist on the remote instance. There might be an issue with how it fetches them from the remote instance, or how it parses the received list. I'll have a look, and prepare a patch for the next minor release.
The cause was that Sonarr always adds a trailing slash (/
for POSIX paths, \
for Windows paths) to the local and remote paths of remote path mappings. If the corresponding values in the Buildarr configuration did not have these trailing slashes, then Buildarr would not detect that the remote path mapping already exists, and will always try to create it.
I have just merged a PR resolving this issue, which will be included in the next minor release, hopefully within the next day or two.
Thanks for waiting. The fix for this issue has been released as:
callum027/buildarr:0.7.6
(or update your local container if using latest
)buildarr-installer-0.7.6-x64.exe
buildarr-sonarr==0.6.4
Please give the new version a try to check that it resolves your issue.
As some time has passed since this has been addressed, I will now close this issue.
Let me know if you have any more problems with either this issue, or using Buildarr in general.
the first time buildarr is ran it adds the mappings correctly but any consequent runs will fail with the following. the temporal fix is to comment the config entry or remove the mapping from sonarr itself everytime