On Saturday, 18 May 2013 at 20:44, Gregory Smith via Hallon wrote:
I'm new to Hallon and for the most part things are working great. I have come across an issue where some artists simply won't load. It seems like it's a small subset, say out of a playlist of 40 tracks, I found 4-5.
This happens sometimes.
libspotify makes no guarantee that an object will ever load. It’s not at all uncommon that an object takes over 30 seconds to load, or never loads at all. This may seem strange at first, but considering libspotify is built for a GUI environment, where objects are simply available until they’re loaded, it’s usually not a big deal if a track doesn’t load in this environment.
I’ve been told this is simply how libspotify behaves, and the reason is because the backend might have (at times) problems with specific tasks. These issues are usually resolved after a while, so trying another day might even fix the problem! I’m not aware of any way to work around this, or how to make libspotify more reliable.
It might even be the case that if you try to load unavailable objects from another account or from within another country it’ll work just fine.
Some examples include:
spotify:artist:0YrtvWJMgSdVrk3SfNjTbx | Death Cab for Cutie
spotify:artist:3DiDSECUqqY1AuBP8qtaIa | Alicia Keys
Can anyone verify that they are able to load these artists? I have checked and double checked the URIs are correct. I've blasted my local Hallon cache in my project's /tmp/ directory. Is there anywhere else there may be cached data that could be causing this or is this an issue with some combination of libspotify/Hallon?
Even having verification that others can load these artists would be a huge help as I try to debug this.
I had no issues loading these.