Iris ignores lookup(playlist) track data when browsing, pulls track data one-by-one, resulting in hanging spinner in the UI #692
Description
Describe the bug
This comment WRT "slow browsing" using the Tidal backend sums up what I think is going on.
To Reproduce
- Setup Iris frontend, and a Tidal backend in Mopidy.
- In Iris do: Browse --> Tidal --> Moods --> (select mood)
- Get loading spinner, never recovers
Expected behavior
That tracks load and display quickly. Internally, I think Iris should use the results of lookup(playlist) to show track lists.
Environment details:
- OS: Raspberry Pi
- Browser: Firefox
- Iris version: Current PYPI version.
Additional context
At present, the mopidy-tidal backend doesn't return track data when doing lookup(playlist) (moods are just a type of playlist). Even after implementing that, it is ignored by Iris, which will use the track ref list obtained by browse(playlist), and then do a lookup(track) for each track. The Tidal API seems rate limited, so this takes a long time, and Iris (I presume) times out internally. If I artificially limit browse(playlist) to return 5 tracks, it works. But some of these mood playlists are 100+ tracks.