orontee
commented
5 months ago First thank you very much for your feedbacks!
Sorry to hear about this playlist problem. I don't have a Spotify account so I never checked myself and I can't remember users validating that it works correctly... But the beauty of Mopidy is that it should abstract all those APIs, so "remontons-nous les manches"!
Can you please give me some tips to understand how to make debug the app , and which tools do you use to create it.
First, you should post more information:
- A complete log if possible (Completing a playlist description calls the JSON-RPC command
core.playlists.lookup, one sees that it was the 17-th sent commands but what happens next from the log point of view?? There should be a log starting with "Fetching tracks of playlist with URI..." followed by a sequence ofcore.library.lookupJSON-RPC commands) - The JSON object received by 17-th command (Attach a file if the object is too big and see me a private message if you're concerned about possible secrets or private data, I won't keep the file) and the related following commands
Second, if you want to debug by yourself, you'll find some tips in the "debugging" section of the contributing guide. But it's rather rough tooling that's suggested there: pdb is a command line debugger.
So for a Python starter (welcome onboard!) the simplest thing to do is to find a recent Linux box, install Builder, click "Add a project", enter the Github URL of Argos, click the run button and... that's all! All dependencies installed magically, interactive debug, etc. :warning: Disclaimer, I never tried on a Windows box.
Otherwise you can use your preferred editor, learn to build the application (explained in that guide too). Then add temporary logs to the standard output: All modules have a LOGGER global variable you can use to print stuff...
Read https://github.com/orontee/argos/blob/main/argos/controllers/playlists.py#L180 and the private function it calls https://github.com/orontee/argos/blob/main/argos/controllers/playlists.py#L200.
About your second question:
When using Flatpak, you should think "containers" or "sandbox". So to access the GSettings of the application running in the sandbox, first enter the sandbox.
For example, on a computer where Argos is installed as a DEB package for daily use and as Flatpak to develop (peitho is a Linux box):
matthias@peitho:~/Projets/argos$ gsettings get io.github.orontee.Argos mopidy-base-url
'http://192.168.1.45'
matthias@peitho:~/Projets/argos$ flatpak run --devel --command=sh io.github.orontee.Argos
[📦 io.github.orontee.Argos ~]$ gsettings get io.github.orontee.Argos mopidy-base-url
'http://localhost:6680'
[📦 io.github.orontee.Argos ~]$ exit
exit
matthias@peitho:~/Projets/argos$ Note I didn't checked on a Windows box but I don't expect things to be that different!
Please keep me informed of your progress.
MaxCreeger32
kingosticks
Hello,
I really love this software that I discovered last week. Thank you for this job ! I have noticed that loading spotify playlists never finish loading titles, in the playlists tab. The waiting wheel with the message "Loading playlist tracks..." stay all along the time and the tracks are never displayed. when I look at the debug log I only see this :
the message is well received by argos
and If i Look in the mopidy journal :
so the message sent seems ok and is received by Argos. I tried to watch the code but I did not see (because I am not used to python and GTK) where is the problem.
Can you please give me some tips to understand how to make debug the app , and which tools do you use to create it.
Another thing : I do not manage to see the configuration items of Argos (which is installed via flatpak on WSL under Win11).
even in Gsettings
Thank you for your help.