Better error reporting

[Dame1701]

I've just spent several hours integrating AudioMuse with my own music player. The integration is finally working well, but it was quite a painful experience getting there. There seems to be a tendency to swallow exceptions and failures. I had to dive into the container logs to see what the actual problem was.

The most frustrating example of this was trying to generate a playlist using OLLAMA. If something fails with OLLAMA, perhaps a bad request or the wrong URL passed through or the specified LLM model missing etc. Instead of raining an error, AudioMuse just returns a playlist with some random tracks in my library.

It would be far more useful if an appropriate error was returned with a clear indication of what went wrong. The current behaviour is misleading and makes permeating such an error through an integrated app almost impossible.

The only real difference I see when it encounters an error is that a playlist is returned immediately whereas when it's actually working it will take a while to generate something.

If you could improve this error handling it would make integration a lot more straightforward.

Once it's working it does seem to work well, so great job on that front. I think it just needs a little polishing with regards to exception handling and propagation.

[NeptuneHub]

Hi, and thanks for the feedback, error handling feature is tracked here:

• [FEATURE] Better error messages in the web interface #107

It need a bit of refactoring in order to handled in a centralized way, so it will not happen in the near future but is for sure on my plan.

I'm closing this disucssion as a duplicate, if you want to add other details please directly use the issue ticket.

[Dame1701]

I just noticed it's been posted before, sorry about that. Thanks for replying. I'll track that issue.