logs archiveBotHelp.net / Freenode / #mopidy / 2015 / September / 4 / 1
jodal
death to raspbian wheezy. please get your *** together and release a raspbian jessie image.
I guess <1% of raspbian wheezy users manage to use the wheezy dist from apt.mopidy.com instead of the jessie dist.
then they get too old requests and broken mopidy-spotify
well... let's have mopidy crash immediately if requests is too old:
adamcik
btw, I'm now at some ~40 test failures instead of 100+ out of 125 for the local core proxy yak shaving...
and that cleanup can probably go straight into develop as well
jodal
that's a great strategy to get large changes in: chop off anything that can be chopped off and get it in alone
adamcik
I just need to figure out what to do with merging / rebasing it back in
the gapless history is getting quite messy
Gamma_
Anyone that could help me with a bit of troubleshooting? Seems like a screwed up somewhere... I can't seem to get the mopidy-spotify loaded, it just does not what to load, even if it is in the conf file
Loading config from /etc/xdg/mopidy/mopidy.conf failed; it does not exist <--- Also getting that now that I checked the log.
jodal
Gamma_: that's just "INFO", not "WARNING" or "ERROR"
Gamma_: what kind of system are you on? how did you install mopidy and mopidy-spotify?
Gamma_
Debian, apt-get
tkem
jodal: +1 for raspbian jessie, whether one likes systemd or not ;-)
jodal
Gamma_: from official debian, not from apt.mopidy.com?
Gamma_: and can you paste your log in a pastebin and provide the link to it? I have nothing to go on regarding mopidy-spotify not working for you yet
Gamma_
From apt.mopidy.com. And give me a sec and ill drop it into pastebin.
tkem
or, better: +1 for an official raspbian jessie image released by the raspberry pi foundation; my raspbian runs fine after doing a dist-upgrade to jessie ;-)
jodal
tkem: it's odd it isn't already released... jessie became stable more than four months ago
that means that wheezy has less than eight months left of security support
tkem
jodal: yes, it's odd, and somewhat annoying, but there isn't much we can do i guess
Gamma_
jodal, http://pastebin.com/SuK3qXDT But while looking at the log now, it seems like its ignore my config file?
jodal
Gamma_: where's your config file located?
Gamma_: there's no warnings/errors at all in the log, and "Ignoring unknown config section: spotify" indicates that you haven't installed mopidy-spotify: sudo apt install mopidy-spotify
adamcik
yay, all the tests pass now :-)
jodal
adamcik: nice :-)
adamcik
I mostly got away with just replacing the assert* things with custom ones like self.assertStateEqual self.assertCurrentTrackEqual etc
which means that those are the only bits that really need to care about futures
but nitpick question: self.assertStateEqual(PlaybackState.STOPPED) or self.assertState(PlaybackState.STOPPED) or self.assertStateIs(PlaybackState.STOPPED)
I've currently called things assert*Equal, but that implies to values in my head
*two
Gamma_
jodal, config is located at .config/mopidy/mopidy.conf
And pretty sure I had it installed, but ran it again now and recieved the following :
The following packages have unmet dependencies:
mopidy-spotify : Depends: python-spotify (>= 2.0.2) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
adamcik
jodal: biggest problem with finding things like these test cases is the endless merge conflicts :/
I'll get it once applying my stash to develop and probably again going back to my branch
perhaps I should just be commiting things like this in the branch I "discover" them in and cherrypick instead?
jodal
Gamma_: my guess: you're running debian/raspbian wheezy (oldstable), and are trying to install packages for jessie (stable)
Gamma_: 1) sudo sed -i -e 's/stable/wheezy/' /etc/apt/sources.list.d/mopidy.list 2) sudo apt-get update 3) sudo apt-get install mopidy-spotify
adamcik: I agree that *Equal implies two values. also might consider snake_case even though unittest is camelCase?
adamcik
so assert_state assert_current_track assert_current_track_not etc
Gamma_
jodal. It worked! Thanks. I have a question tho. I have been running it constantly for the last 2 months without any issues or changes. Did something change in the last week or so that would have caused this issue?
adamcik
mopidy-spotify 2.0 was released
as was pyspotify
Gamma_
Ah. That would make sense then.
jodal
Gamma_: mopidy-spotify 2 was released a couple of weeks ago. it is quite different from mopidy-spotify 1, so the built packages for jessie no longer works on wheezy like they used to do
Gamma_: and I also pruned some backported packages from the jessie dist, as they're not necessary on jessie
(and then reintroduced a couple of them, while we wait for travis-ci to either start using our wheezy dist on their ubuntu 12.04 builders or get their builders up to ubuntu 14.04)
backports, like newer tornado and requests
adamcik
btw, we should fix the number of tests we have to the current level
2048 passed in 9.51 seconds :P
or double them
txomon|sauron
haha, but all in one commit!!!
adamcik
tkem: you also taking the day off for projects etc? :-)
tkem
i'm usually off on friday, since i cut down to 30 work hours/week about a year ago
more time for family, friends, and mopidy ;-)
adamcik
sounds like a good trade-off :-) mostly the family and friends, but mopidy doesn't hurt either
jodal
I´m home three days a week with my eight month old boy... leaves quite a bit extra time for hacking :-)
tkem
jodal: that's also a good arrangement, congratulations!
adamcik
downside of not being back in Norway, I "only" get four or five weeks of paternity, but way better than the legal minimum of one day at least :-)
jodal
I have three days a week off in aug-oct, and will be home the entirety of nov and dec
adamcik: have to feed and put the little one to bed before reviewing that ;-)
tkem: will soon look at the -images PR
adamcik
family first, np :-)
tkem
jodal: take your time, thanks for your efforts so far!
adamcik
down to 2 failing tests with my refactored next code
so close...
make that one
and none!
txomon|sauron
haha
jodal
adamcik: that's another intermediate PR? :-)
adamcik
no, not really
was just debugging the following http://dpaste.com/15Y8XB8
trying to understand why I need the .get() on the next
but makes sense
just had to create that paste to try and ask about it to make it fit together in my head
basically any call that has async things in it _must_ be called with a .get() in tests to ensure we queue the audio events before the get_current_track etc
woot - all that prep work is paying off
same change for previous only broke 8 tests
jodal
the snowball is growing quickly on the gapless branch it seems :-) can't stop this one hitting develop!
adamcik
98 failed for play - thats more like it or something
guesting
Using ncmpcpp, how do I have a default ordering of the playlist? Everything is in order in the media library, but when I add an album to the playlist, the order completely changes. How can I preserve the ordering or have a default ordering for the playlist in the config?
From what I hear, it adds it in order of filename, but the filenames start with track numbers and it's still out of order
adamcik
what backend are you adding from, and is it an "album" item you are adding or an expanded folder with the album?
guesting
Backend? You mean mopidy?
An album is me going to the media library (4) and going to an album artist in the first column, then hitting space bar or enter on the middle column (album)
Right now I have my bindings file to just do Ctrl-v scroll_down * 10 and then press_enter
but obviously it's a bit silly
adamcik
as in spotify, local music, radio, etc?
shakar
Hi, I'm trying to get the hang of pyspotify and create a playlist. but when I run "session.playlist_container.append('some string')" I end up with "spotify.error.LibError: Invalid input" -- can anyone help me understand what might be wrong?
guesting
adamcik: Spotify and local
kingosticks
shakar: you probably need to dump the rest of your code in a pastebin
or your 'some string' playlist name is illegal somehow
shakar
the last string I tried was "SAFENAME" -- alright, pastebin acomin'
kingosticks
hehe
shakar
http://pastebin.com/wK7NRdtn
kingosticks: anything obvious? I thought maybe it was some kind of failure to initialize problem, so I tried throwing in a self.session.playlist_container.load() before the append, with no change
« prev 1 2 next »