[BUG] Mixed-Metadata error preventing disk scan

[PrivatePuffin]

Tubifarry Version

develop

Lidarr Version

latest

Operating System

Docker

Bug Description

Disk scanning gets cancelled with an error.

I have no idea if and how its related to tubifary, but it is mentioned in the log output
Just wanting to throw it out here for information purposes.

Steps to Reproduce

Run tubifary and tubifary develop

Then try to run a disk scan and have "bad luck"

Expected Behavior

It shouldn't throw any errors that prevent further disk scanning

Log Files

Logs

System.InvalidOperationException: Sequence contains no elements
   at System.Linq.ThrowHelper.ThrowNoElementsException()
   at System.Linq.Enumerable.Max[TSource](IEnumerable`1 source, Func`2 selector)
   at Tubifarry.Metadata.Proxy.Mixed.MixedMetadataProxy.GetCandidateProxies(Func`2 supportSelector)
   at Tubifarry.Metadata.Proxy.Mixed.ProxyDecisionHandler`1.ExecuteSearch()
   at NzbDrone.Core.MediaFiles.TrackImport.Identification.CandidateService.GetRemoteCandidates(LocalAlbumRelease localAlbumRelease) in ./Lidarr.Core/MediaFiles/TrackImport/Identification/CandidateService.cs:line 239
   at NzbDrone.Core.MediaFiles.TrackImport.Identification.IdentificationService.IdentifyRelease(LocalAlbumRelease localAlbumRelease, IdentificationOverrides idOverrides, ImportDecisionMakerConfig config) in ./Lidarr.Core/MediaFiles/TrackImport/Identification/IdentificationService.cs:line 203
   at NzbDrone.Core.MediaFiles.TrackImport.Identification.IdentificationService.Identify(List`1 localTracks, IdentificationOverrides idOverrides, ImportDecisionMakerConfig config) in ./Lidarr.Core/MediaFiles/TrackImport/Identification/IdentificationService.cs:line 134
   at NzbDrone.Core.MediaFiles.TrackImport.ImportDecisionMaker.GetImportDecisions(List`1 musicFiles, IdentificationOverrides idOverrides, ImportDecisionMakerInfo itemInfo, ImportDecisionMakerConfig config) in ./Lidarr.Core/MediaFiles/TrackImport/ImportDecisionMaker.cs:line 153
   at NzbDrone.Core.MediaFiles.DiskScanService.Scan(List`1 folders, FilterFilesType filter, Boolean addNewArtists, List`1 artistIds) in ./Lidarr.Core/MediaFiles/DiskScanService.cs:line 186
   at NzbDrone.Core.MediaFiles.DiskScanService.Execute(RescanFoldersCommand message) in ./Lidarr.Core/MediaFiles/DiskScanService.cs:line 310
   at NzbDrone.Core.Messaging.Commands.CommandExecutor.ExecuteCommand[TCommand](TCommand command, CommandModel commandModel) in ./Lidarr.Core/Messaging/Commands/CommandExecutor.cs:line 115
   at System.Dynamic.UpdateDelegates.UpdateAndExecuteVoid3[T0,T1,T2](CallSite site, T0 arg0, T1 arg1, T2 arg2)
   at NzbDrone.Core.Messaging.Commands.CommandExecutor.ExecuteCommands() in ./Lidarr.Core/Messaging/Commands/CommandExecutor.cs:line 42

Screenshots

Screenshots

[TypNull]

It’s possible, but could you share the actual log files or at least the full error message? I rewrote everything in the Proxy system, so there might be an issue there. Also, did you enable MetaMix or any other metadata provider? Or is MetaMix the only one currently active?
Additionally, please make sure to fill out the issue form correctly next time. What version of the develop branch are you using, and what is the latest version of Lidarr you have installed?

[PrivatePuffin]

Additionally, please make sure to fill out the issue form correctly next time.

As stated, I did not intent to qualify for any developer attention and just wanted to drop this here in case someone was interested in it.
This mean purposefully did not fill out the form, because my developer attention is needed elsewhere, nor did I expect it to be threated with the same attention as a correct bug report

I appreciate the attention, but the choice not to fill out the form correctly was done on purpose.
Mostly just asking if anyone else is seeing this, or this being a niche issue. As I dont have time to file fully qualifying bugreuports for each and every issue I encounter.

[TypNull]

That's unfortunate, I can't determine whether this is a valid bug based on the current information.
For things like this you typically don't file formal bug reports. Instead, use the discussion section or share it in the Servarr Discord to see if others are experiencing the same problem.

[PrivatePuffin]

I missed that discussions were open. Thanks for the conversion