Album Search Broken due to ResourceMapping #463

Closed
opened 2026-02-20 01:03:41 -05:00 by deekerman · 12 comments
Owner

Originally created by @Qstick on GitHub (Mar 21, 2019).

Describe the bug
Calls to album search fail due to resource mapping. Currently these are failing out at AlbumResource.cs Line 60 because an album search returns album objects which do not yet have releases, or an artistId in DB. So the call to release service fails and the lazyload of artist fails.

ex. http://localhost:8686/api/v1/album/lookup?apikey={redacted}&term=kiss

Expected behavior
Album search should return search results without adding items to the DB. Null checks likely needed to be added to the resource mapping so that results are still returned.

This is likely what is killing Ombi on nightly.

Originally created by @Qstick on GitHub (Mar 21, 2019). **Describe the bug** Calls to album search fail due to resource mapping. Currently these are failing out at `AlbumResource.cs` Line 60 because an album search returns album objects which do not yet have releases, or an artistId in DB. So the call to release service fails and the lazyload of artist fails. ex. http://localhost:8686/api/v1/album/lookup?apikey={redacted}&term=kiss **Expected behavior** Album search should return search results without adding items to the DB. Null checks likely needed to be added to the resource mapping so that results are still returned. This is likely what is killing Ombi on nightly.
deekerman 2026-02-20 01:03:41 -05:00
Author
Owner

@mouzzampk2014-zz commented on GitHub (Mar 21, 2019):

Hi, I'm using latest tag shall I switch to develop tag for a fix? I'm on Dockers.

@mouzzampk2014-zz commented on GitHub (Mar 21, 2019): Hi, I'm using latest tag shall I switch to develop tag for a fix? I'm on Dockers.
Author
Owner

@Qstick commented on GitHub (Mar 21, 2019):

No, nightly is broken

@Qstick commented on GitHub (Mar 21, 2019): No, nightly is broken
Author
Owner

@mouzzampk2014-zz commented on GitHub (Mar 21, 2019):

Oh okay I will wait for 0.7 😁

On Fri, 22 Mar 2019, 03:06 Qstick, notifications@github.com wrote:

No, nightly is broken


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/lidarr/Lidarr/issues/690#issuecomment-475478371, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AqfBrWWSQPlHy0wgnKuV3UxStgJWgZEaks5vZEiwgaJpZM4cCtsH
.

@mouzzampk2014-zz commented on GitHub (Mar 21, 2019): Oh okay I will wait for 0.7 😁 On Fri, 22 Mar 2019, 03:06 Qstick, <notifications@github.com> wrote: > No, nightly is broken > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/lidarr/Lidarr/issues/690#issuecomment-475478371>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AqfBrWWSQPlHy0wgnKuV3UxStgJWgZEaks5vZEiwgaJpZM4cCtsH> > . >
Author
Owner

@Qstick commented on GitHub (Mar 21, 2019):

0.5.0.583 should be working

@Qstick commented on GitHub (Mar 21, 2019): 0.5.0.583 should be working
Author
Owner

@mouzzampk2014-zz commented on GitHub (Mar 24, 2019):

Is this fixed? :)

@mouzzampk2014-zz commented on GitHub (Mar 24, 2019): Is this fixed? :)
Author
Owner

@ta264 commented on GitHub (Mar 24, 2019):

Should be fixed on nightly

@ta264 commented on GitHub (Mar 24, 2019): Should be fixed on nightly
Author
Owner

@mouzzampk2014-zz commented on GitHub (Mar 24, 2019):

I will give a go in an hour. Thank you so much

@mouzzampk2014-zz commented on GitHub (Mar 24, 2019): I will give a go in an hour. Thank you so much
Author
Owner

@ta264 commented on GitHub (Mar 24, 2019):

Make sure to switch container image if you're not on nightly currently otherwise you'll have problems if you ever recreate the container. You want linuxserver/lidarr:preview

@ta264 commented on GitHub (Mar 24, 2019): Make sure to switch container image if you're not on nightly currently otherwise you'll have problems if you ever recreate the container. You want `linuxserver/lidarr:preview`
Author
Owner

@mouzzampk2014-zz commented on GitHub (Mar 24, 2019):

Yes I'm on preview currently so should be okay

@mouzzampk2014-zz commented on GitHub (Mar 24, 2019): Yes I'm on preview currently so should be okay
Author
Owner

@mouzzampk2014-zz commented on GitHub (Mar 24, 2019):

Nope still same issue :( and I am on 0.5.0.753

@mouzzampk2014-zz commented on GitHub (Mar 24, 2019): Nope still same issue :( and I am on 0.5.0.753
Author
Owner

@ta264 commented on GitHub (Mar 24, 2019):

Hmm, it was working for me

@ta264 commented on GitHub (Mar 24, 2019): Hmm, it was working for me
Author
Owner

@mouzzampk2014-zz commented on GitHub (Mar 24, 2019):

Hmm, it was working for me

Let me clear my log and retry again. Must be fixed its just me been thick. Just give me couple of hours. Thanks again

@mouzzampk2014-zz commented on GitHub (Mar 24, 2019): > Hmm, it was working for me Let me clear my log and retry again. Must be fixed its just me been thick. Just give me couple of hours. Thanks again
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Lidarr#463
No description provided.