Posts: 156
Threads: 6
Joined: Apr 2018
Reputation:
11
No doubt, the internet & music streaming has raised the profile of bands far quicker than word of mouth in the schoolyard or reading the gig reviews in the music press ever did.
I still miss the record store experience apart from when they didn't have what I wanted in stock, which happened frequently as I have never listened to mainstream music.
Posts: 23
Threads: 3
Joined: Feb 2019
Reputation:
0
09-06-2019, 08:54 AM
(This post was last modified: 09-06-2019, 01:26 PM by IT-Andy52.)
Hi
I have to admit, that I have no idea of "How Linux works" - I had copy and pasted RafaPolit's instructions - noise plays, however when testing the services I get:
pi@moode:~ $ systemctl status spotify-connect-web.service
● spotify-connect-web.service
Loaded: loaded (/lib/systemd/system/spotify-connect-web.service; disabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2019-09-06 10:41:34 CEST; 6s ago
Process: 6150 ExecStart=/home/pi/spotify/spotify-connect.sh (code=exited, status=203/EXEC)
Main PID: 6150 (code=exited, status=203/EXEC)
I am (almost) positive, that I have no typos - Pls help
Oh and I changed line in main.py to gevent.pywsgi and did use SpotifyMaster
Andreas
Posts: 113
Threads: 7
Joined: Apr 2018
Reputation:
3
I just tried this with MoOde 6+ and it worked still.
Posts: 113
Threads: 7
Joined: Apr 2018
Reputation:
3
(09-06-2019, 08:54 AM)IT-Andy52 Wrote: Hi
I have to admit, that I have no idea of "How Linux works" - I had copy and pasted RafaPolit's instructions - noise plays, however when testing the services I get:
pi@moode:~ $ systemctl status spotify-connect-web.service
● spotify-connect-web.service
Loaded: loaded (/lib/systemd/system/spotify-connect-web.service; disabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2019-09-06 10:41:34 CEST; 6s ago
Process: 6150 ExecStart=/home/pi/spotify/spotify-connect.sh (code=exited, status=203/EXEC)
Main PID: 6150 (code=exited, status=203/EXEC)
I am (almost) positive, that I have no typos - Pls help
Oh and I changed line in main.py to gevent.pywsgi and did use SpotifyMaster
Andreas
Well, the main.py change is no longer needed as this was addressed by forking the repo and doing the change already. Can you please follow the instructions exactly as in per the README of the repo?
That should be enough. I have just tried this on a fresh install of moode and it worked as expected (you don't need to change any lines, just copy the instructions line by line from the main page of the GitHub link)
Posts: 113
Threads: 7
Joined: Apr 2018
Reputation:
3
By the way, the librespot-org guys have already wrapped the liberspot library in a java environment and that is reported to support gapless playback. I haven't yet tried it, if someone does, please report. It could be much simpler than this at this point.
Posts: 2
Threads: 0
Joined: Mar 2020
Reputation:
1
Hi,
I originally used the Spotify Connect solution builtin to Moode but wanted some gapless goddness so I thought I'd give this a go. I've managed to get everything built and installed, and when I start up the spotify-connect-web service I see the following messages:
Loading Spotify library...
Last.fm: incomplete credentials, not launched
Device has no native mute
min_volume_range: 0
Using libspotify_embedded version: release-esdk-1.20.0-v1.20.0-g594175d4
SpInit: 0
playback_volume: 65535
corected_playback_volume: 100
public key: 7SvrwjUT64UENxNyDtoAt/mwEohLOl1dS5W75hniytF2hiQ0yaCoHNlDhjFHW9I1uOZLfp4BBBHdId5OhGTFhjQioD6JSyytWG5Nt1EDJX60jUAiYEruN83wMpoh7MND
device id: 9b14e273-68a3-439e-9383-d690b386948b
remote name: moOde Connect
account req: PREMIUM
device type: AUDIODONGLE
Which looks good to me. Until I select 'devices available' on Spotify on my phone when i get the following messages:
[2020-03-26 14:16:26,066] ERROR in app: Exception on /login/_zeroconf [GET]
Traceback (most recent call last):
File "/home/pi/.local/lib/python2.7/site-packages/flask/app.py", line 1988, in wsgi_app
response = self.full_dispatch_request()
File "/home/pi/.local/lib/python2.7/site-packages/flask/app.py", line 1641, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/home/pi/.local/lib/python2.7/site-packages/flask_cors/extension.py", line 188, in wrapped_function
return cors_after_request(app.make_response(f(*args, **kwargs)))
File "/home/pi/.local/lib/python2.7/site-packages/flask/app.py", line 1544, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/home/pi/.local/lib/python2.7/site-packages/flask/app.py", line 1639, in full_dispatch_request
rv = self.dispatch_request()
File "/home/pi/.local/lib/python2.7/site-packages/flask/app.py", line 1625, in dispatch_request
return self.view_functions[rule.endpoint](**req.view_args)
File "main.py", line 221, in login_zeroconf
return get_info()
File "main.py", line 251, in get_info
'remoteName': zeroconf_vars['remoteName']
File "/home/pi/.local/lib/python2.7/site-packages/flask/json.py", line 254, in jsonify
if current_app.config['JSONIFY_PRETTYPRINT_REGULAR'] and not request.is_xhr:
File "/home/pi/.local/lib/python2.7/site-packages/werkzeug/local.py", line 347, in __getattr__
return getattr(self._get_current_object(), name)
AttributeError: 'Request' object has no attribute 'is_xhr'
::ffff:192.168.1.25 - - [2020-03-26 14:16:26] "GET /login/_zeroconf?action=getInfo HTTP/1.1" 500 426 0.044331
I get this block of messages everytime I select the 'devices available' option. I am on a fresh install of the current Moode (6.4.2) and the avahi service is started and a sudo systemctl status avahi-spotify-connect-multiuser.service gives me:
● avahi-spotify-connect-multiuser.service
Loaded: loaded (/lib/systemd/system/avahi-spotify-connect-multiuser.service; disabled; vendor preset: enabled)
Active: active (running) since Thu 2020-03-26 14:11:28 CET; 1h 9min ago
Main PID: 1461 (avahi-publish-s)
Tasks: 1 (limit: 2200)
Memory: 364.0K
CGroup: /system.slice/avahi-spotify-connect-multiuser.service
└─1461 /usr/bin/avahi-publish-service TestConnect _spotify-connect._tcp 4000 VERSION=1.0 CPath=/login/_zeroconf
Mar 26 14:11:28 moode systemd[1]: Started avahi-spotify-connect-multiuser.service.
Mar 26 14:11:29 moode avahi-publish-service[1461]: Established under name 'TestConnect'
I have read through the thread and can't find anything like this. I did try changing from gevent.wsgi import WSGIServer to from gevent.pywsgi import WSGIServer just in case but without luck.
Any help would be really appreciated, mixed DJ albums really don't sound the same when they're not gapless ;-)
Posts: 2
Threads: 0
Joined: Mar 2020
Reputation:
1
03-27-2020, 08:41 AM
(This post was last modified: 03-27-2020, 09:11 AM by doodydoo.)
(03-26-2020, 02:28 PM)doodydoo Wrote: Hi,
I originally used the Spotify Connect solution builtin to moOde but wanted some gapless goddness so I thought I'd give this a go. I've managed to get everything built and installed, and when I start up the spotify-connect-web service I see the following messages:
Loading Spotify library...
Last.fm: incomplete credentials, not launched
Device has no native mute
min_volume_range: 0
Using libspotify_embedded version: release-esdk-1.20.0-v1.20.0-g594175d4
SpInit: 0
playback_volume: 65535
corected_playback_volume: 100
public key: 7SvrwjUT64UENxNyDtoAt/mwEohLOl1dS5W75hniytF2hiQ0yaCoHNlDhjFHW9I1uOZLfp4BBBHdId5OhGTFhjQioD6JSyytWG5Nt1EDJX60jUAiYEruN83wMpoh7MND
device id: 9b14e273-68a3-439e-9383-d690b386948b
remote name: moOde Connect
account req: PREMIUM
device type: AUDIODONGLE
Which looks good to me. Until I select 'devices available' on Spotify on my phone when i get the following messages:
[2020-03-26 14:16:26,066] ERROR in app: Exception on /login/_zeroconf [GET]
Traceback (most recent call last):
File "/home/pi/.local/lib/python2.7/site-packages/flask/app.py", line 1988, in wsgi_app
response = self.full_dispatch_request()
File "/home/pi/.local/lib/python2.7/site-packages/flask/app.py", line 1641, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/home/pi/.local/lib/python2.7/site-packages/flask_cors/extension.py", line 188, in wrapped_function
return cors_after_request(app.make_response(f(*args, **kwargs)))
File "/home/pi/.local/lib/python2.7/site-packages/flask/app.py", line 1544, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/home/pi/.local/lib/python2.7/site-packages/flask/app.py", line 1639, in full_dispatch_request
rv = self.dispatch_request()
File "/home/pi/.local/lib/python2.7/site-packages/flask/app.py", line 1625, in dispatch_request
return self.view_functions[rule.endpoint](**req.view_args)
File "main.py", line 221, in login_zeroconf
return get_info()
File "main.py", line 251, in get_info
'remoteName': zeroconf_vars['remoteName']
File "/home/pi/.local/lib/python2.7/site-packages/flask/json.py", line 254, in jsonify
if current_app.config['JSONIFY_PRETTYPRINT_REGULAR'] and not request.is_xhr:
File "/home/pi/.local/lib/python2.7/site-packages/werkzeug/local.py", line 347, in __getattr__
return getattr(self._get_current_object(), name)
AttributeError: 'Request' object has no attribute 'is_xhr'
::ffff:192.168.1.25 - - [2020-03-26 14:16:26] "GET /login/_zeroconf?action=getInfo HTTP/1.1" 500 426 0.044331
I get this block of messages everytime I select the 'devices available' option. I am on a fresh install of the current moOde (6.4.2) and the avahi service is started and a sudo systemctl status avahi-spotify-connect-multiuser.service gives me:
● avahi-spotify-connect-multiuser.service
Loaded: loaded (/lib/systemd/system/avahi-spotify-connect-multiuser.service; disabled; vendor preset: enabled)
Active: active (running) since Thu 2020-03-26 14:11:28 CET; 1h 9min ago
Main PID: 1461 (avahi-publish-s)
Tasks: 1 (limit: 2200)
Memory: 364.0K
CGroup: /system.slice/avahi-spotify-connect-multiuser.service
└─1461 /usr/bin/avahi-publish-service TestConnect _spotify-connect._tcp 4000 VERSION=1.0 CPath=/login/_zeroconf
Mar 26 14:11:28 moode systemd[1]: Started avahi-spotify-connect-multiuser.service.
Mar 26 14:11:29 moode avahi-publish-service[1461]: Established under name 'TestConnect'
I have read through the thread and can't find anything like this. I did try changing from gevent.wsgi import WSGIServer to from gevent.pywsgi import WSGIServer just in case but without luck.
Any help would be really appreciated, mixed DJ albums really don't sound the same when they're not gapless ;-)
Well I've managed to surprise myself and fix this on my own so I'll document what I did just in case anyone else has the same problem.
After working through the error messages and doing a few searches I arrived here: https://stackoverflow.com/questions/6013...-to-heroku which mentions an upgrade to the werkzurg python package which causes problems with versions of the flask package below 0.12.4. The suggestions for fixing this issue included upgrading to flask v1.0.0 and higher or downgrading werkzeug to below 1.0.
Rafa's requirements.txt includes the line Flask==0.11.1 so upgrading to V1 probably isn't a good idea so I added wekzeug<1.0, re-ran pip install -r requirements.txt, rebooted (not strictly necessarily but whatever), started both the services and now it works just fine, gapless goodness achieved!!
I'll open an issue on github so Rafa can take a look at it and verify what I've done but right now it works just fine.
Just to be complete I installed this on a fresh copy of moOde 6.4.2 on a Raspberry Pi 3B+ with an IQAudio Pi-Dac+. The only change I made to the procedure on github was to change the hw:1 to hw:0 on the slave -> pcm entry in /etc/asound.conf, mine looks like this now:
pcm.softvol {
type softvol
slave {
pcm "hw:0"
}
control {
name "Master"
card 0
}
}
Thanks to Rafa for all your work, it's so good to get gapless playback, it makes such a difference and thanks to Tim, I am so happy with moOde, it gives me everything I need and a whole lot more. Just need to get gapless playback for Spotify baked in ;-)
Posts: 8
Threads: 2
Joined: Jan 2020
Reputation:
0
06-30-2020, 07:50 PM
(This post was last modified: 06-30-2020, 07:51 PM by dml3334.)
Hi.
Firstly, thanks for your work!
I am running Moode Audio 6.5.4 and I would like to try your Spotify Connect Web instead of the built-in in Moode. I would like to see, for example, some more activity about the songs in the display. But, although everything looks great at the end of the installation process, it does not appear in the list of the devices to be connected to.
I followed all the steps, but I had to adapt asound.conf to
Code: pcm.softvol {
type softvol
slave {
pcm "hw:0"
}
control {
name "Master"
card 0
}
}
The output of aplay -L is
Code: pi@moode:/etc $ aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
btaplay_dmix
alsaequal
plug_alsaequal
btstream
crossfeed
plug_bs2b
eqfa4p
plug_eqfa4p
invpolarity
softvol
default:CARD=ALSA
bcm2835 ALSA, bcm2835 ALSA
Default Audio Device
sysdefault:CARD=ALSA
bcm2835 ALSA, bcm2835 ALSA
Default Audio Device
dmix:CARD=ALSA,DEV=0
bcm2835 ALSA, bcm2835 ALSA
Direct sample mixing device
dmix:CARD=ALSA,DEV=1
bcm2835 ALSA, bcm2835 IEC958/HDMI
Direct sample mixing device
dmix:CARD=ALSA,DEV=2
bcm2835 ALSA, bcm2835 IEC958/HDMI1
Direct sample mixing device
dsnoop:CARD=ALSA,DEV=0
bcm2835 ALSA, bcm2835 ALSA
Direct sample snooping device
dsnoop:CARD=ALSA,DEV=1
bcm2835 ALSA, bcm2835 IEC958/HDMI
Direct sample snooping device
dsnoop:CARD=ALSA,DEV=2
bcm2835 ALSA, bcm2835 IEC958/HDMI1
Direct sample snooping device
hw:CARD=ALSA,DEV=0
bcm2835 ALSA, bcm2835 ALSA
Direct hardware device without any conversions
hw:CARD=ALSA,DEV=1
bcm2835 ALSA, bcm2835 IEC958/HDMI
Direct hardware device without any conversions
hw:CARD=ALSA,DEV=2
bcm2835 ALSA, bcm2835 IEC958/HDMI1
Direct hardware device without any conversions
plughw:CARD=ALSA,DEV=0
bcm2835 ALSA, bcm2835 ALSA
Hardware device with all software conversions
plughw:CARD=ALSA,DEV=1
bcm2835 ALSA, bcm2835 IEC958/HDMI
Hardware device with all software conversions
plughw:CARD=ALSA,DEV=2
bcm2835 ALSA, bcm2835 IEC958/HDMI1
Hardware device with all software conversions
And the ouput of amixer control is;
Code: pi@moode:/etc $ amixer controls
numid=6,iface=MIXER,name='Master'
numid=3,iface=MIXER,name='PCM Playback Route'
numid=2,iface=MIXER,name='PCM Playback Switch'
numid=1,iface=MIXER,name='PCM Playback Volume'
numid=5,iface=PCM,name='IEC958 Playback Con Mask'
numid=4,iface=PCM,name='IEC958 Playback Default'
I would like to use the Bluetooth and/or the jack output of the RPI.
But, in Spotify app, it does not appear as a device to connect. Only then, I get these errors in the status spotify-connect-web.service
Code: pi@moode:/etc $ sudo systemctl status spotify-connect-web.service
● spotify-connect-web.service
Loaded: loaded (/lib/systemd/system/spotify-connect-web.service; disabled; vendor preset: enabled)
Active: active (running) since Tue 2020-06-30 21:37:36 CEST; 1min 31s ago
Main PID: 20207 (spotify-connect)
Tasks: 4 (limit: 2200)
Memory: 14.8M
CGroup: /system.slice/spotify-connect-web.service
├─20207 /bin/sh /home/pi/spotify/spotify-connect.sh
└─20209 python main.py --playback_device softvol -m Master --mixer_device_index 0 --bitrate 320 --name moOde Connect --key /home/pi/spotify/spotify-connect-web/spotify_appkey.key
Jun 30 21:38:43 moode spotify-connect.sh[20207]: File "main.py", line 221, in login_zeroconf
Jun 30 21:38:43 moode spotify-connect.sh[20207]: return get_info()
Jun 30 21:38:43 moode spotify-connect.sh[20207]: File "main.py", line 251, in get_info
Jun 30 21:38:43 moode spotify-connect.sh[20207]: 'remoteName': zeroconf_vars['remoteName']
Jun 30 21:38:43 moode spotify-connect.sh[20207]: File "/home/pi/.local/lib/python2.7/site-packages/flask/json.py", line 254, in jsonify
Jun 30 21:38:43 moode spotify-connect.sh[20207]: if current_app.config['JSONIFY_PRETTYPRINT_REGULAR'] and not request.is_xhr:
Jun 30 21:38:43 moode spotify-connect.sh[20207]: File "/home/pi/.local/lib/python2.7/site-packages/werkzeug/local.py", line 347, in __getattr__
Jun 30 21:38:43 moode spotify-connect.sh[20207]: return getattr(self._get_current_object(), name)
Jun 30 21:38:43 moode spotify-connect.sh[20207]: AttributeError: 'Request' object has no attribute 'is_xhr'
Jun 30 21:38:43 moode spotify-connect.sh[20207]: ::ffff:192.168.8.120 - - [2020-06-30 21:38:43] "GET /login/_zeroconf?action=getInfo HTTP/1.1" 500 426 0.019350
What could be happening? What should I change?
Thanks!!
Posts: 8
Threads: 2
Joined: Jan 2020
Reputation:
0
06-30-2020, 09:39 PM
(This post was last modified: 06-30-2020, 09:40 PM by dml3334.)
(06-30-2020, 07:50 PM)dml3334 Wrote: Hi.
Firstly, thanks for your work!
I am running Moode Audio 6.5.4 and I would like to try your Spotify Connect Web instead of the built-in in Moode. I would like to see, for example, some more activity about the songs in the display. But, although everything looks great at the end of the installation process, it does not appear in the list of the devices to be connected to.
I followed all the steps, but I had to adapt asound.conf to
Code: pcm.softvol {
type softvol
slave {
pcm "hw:0"
}
control {
name "Master"
card 0
}
}
The output of aplay -L is
Code: pi@moode:/etc $ aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
btaplay_dmix
alsaequal
plug_alsaequal
btstream
crossfeed
plug_bs2b
eqfa4p
plug_eqfa4p
invpolarity
softvol
default:CARD=ALSA
bcm2835 ALSA, bcm2835 ALSA
Default Audio Device
sysdefault:CARD=ALSA
bcm2835 ALSA, bcm2835 ALSA
Default Audio Device
dmix:CARD=ALSA,DEV=0
bcm2835 ALSA, bcm2835 ALSA
Direct sample mixing device
dmix:CARD=ALSA,DEV=1
bcm2835 ALSA, bcm2835 IEC958/HDMI
Direct sample mixing device
dmix:CARD=ALSA,DEV=2
bcm2835 ALSA, bcm2835 IEC958/HDMI1
Direct sample mixing device
dsnoop:CARD=ALSA,DEV=0
bcm2835 ALSA, bcm2835 ALSA
Direct sample snooping device
dsnoop:CARD=ALSA,DEV=1
bcm2835 ALSA, bcm2835 IEC958/HDMI
Direct sample snooping device
dsnoop:CARD=ALSA,DEV=2
bcm2835 ALSA, bcm2835 IEC958/HDMI1
Direct sample snooping device
hw:CARD=ALSA,DEV=0
bcm2835 ALSA, bcm2835 ALSA
Direct hardware device without any conversions
hw:CARD=ALSA,DEV=1
bcm2835 ALSA, bcm2835 IEC958/HDMI
Direct hardware device without any conversions
hw:CARD=ALSA,DEV=2
bcm2835 ALSA, bcm2835 IEC958/HDMI1
Direct hardware device without any conversions
plughw:CARD=ALSA,DEV=0
bcm2835 ALSA, bcm2835 ALSA
Hardware device with all software conversions
plughw:CARD=ALSA,DEV=1
bcm2835 ALSA, bcm2835 IEC958/HDMI
Hardware device with all software conversions
plughw:CARD=ALSA,DEV=2
bcm2835 ALSA, bcm2835 IEC958/HDMI1
Hardware device with all software conversions
And the ouput of amixer control is;
Code: pi@moode:/etc $ amixer controls
numid=6,iface=MIXER,name='Master'
numid=3,iface=MIXER,name='PCM Playback Route'
numid=2,iface=MIXER,name='PCM Playback Switch'
numid=1,iface=MIXER,name='PCM Playback Volume'
numid=5,iface=PCM,name='IEC958 Playback Con Mask'
numid=4,iface=PCM,name='IEC958 Playback Default'
I would like to use the Bluetooth and/or the jack output of the RPI.
But, in Spotify app, it does not appear as a device to connect. Only then, I get these errors in the status spotify-connect-web.service
Code: pi@moode:/etc $ sudo systemctl status spotify-connect-web.service
● spotify-connect-web.service
Loaded: loaded (/lib/systemd/system/spotify-connect-web.service; disabled; vendor preset: enabled)
Active: active (running) since Tue 2020-06-30 21:37:36 CEST; 1min 31s ago
Main PID: 20207 (spotify-connect)
Tasks: 4 (limit: 2200)
Memory: 14.8M
CGroup: /system.slice/spotify-connect-web.service
├─20207 /bin/sh /home/pi/spotify/spotify-connect.sh
└─20209 python main.py --playback_device softvol -m Master --mixer_device_index 0 --bitrate 320 --name moOde Connect --key /home/pi/spotify/spotify-connect-web/spotify_appkey.key
Jun 30 21:38:43 moode spotify-connect.sh[20207]: File "main.py", line 221, in login_zeroconf
Jun 30 21:38:43 moode spotify-connect.sh[20207]: return get_info()
Jun 30 21:38:43 moode spotify-connect.sh[20207]: File "main.py", line 251, in get_info
Jun 30 21:38:43 moode spotify-connect.sh[20207]: 'remoteName': zeroconf_vars['remoteName']
Jun 30 21:38:43 moode spotify-connect.sh[20207]: File "/home/pi/.local/lib/python2.7/site-packages/flask/json.py", line 254, in jsonify
Jun 30 21:38:43 moode spotify-connect.sh[20207]: if current_app.config['JSONIFY_PRETTYPRINT_REGULAR'] and not request.is_xhr:
Jun 30 21:38:43 moode spotify-connect.sh[20207]: File "/home/pi/.local/lib/python2.7/site-packages/werkzeug/local.py", line 347, in __getattr__
Jun 30 21:38:43 moode spotify-connect.sh[20207]: return getattr(self._get_current_object(), name)
Jun 30 21:38:43 moode spotify-connect.sh[20207]: AttributeError: 'Request' object has no attribute 'is_xhr'
Jun 30 21:38:43 moode spotify-connect.sh[20207]: ::ffff:192.168.8.120 - - [2020-06-30 21:38:43] "GET /login/_zeroconf?action=getInfo HTTP/1.1" 500 426 0.019350
What could be happening? What should I change?
Thanks!!
Well, I discovered in a previous post that I should add
to /home/pi/spotify/spotify-connect-web/requirements.txt and then,
pip -r install requirement.txt
sudo systemctl restart avahi-spotify-connect-multiuser.service
sudo systemctl restart spotify-connect-web.service
Finally, moOde Connect appears as a device to connect Spotify to 
But, the only thing is that, when I play a song in Spotify, neither the name of the song or the cover appear in moOde, as it should be...
Why??
Thanks
Posts: 113
Threads: 7
Joined: Apr 2018
Reputation:
3
(03-27-2020, 08:41 AM)doodydoo Wrote: Well I've managed to surprise myself and fix this on my own so I'll document what I did just in case anyone else has the same problem.
After working through the error messages and doing a few searches I arrived here: https://stackoverflow.com/questions/6013...-to-heroku which mentions an upgrade to the werkzurg python package which causes problems with versions of the flask package below 0.12.4. The suggestions for fixing this issue included upgrading to flask v1.0.0 and higher or downgrading werkzeug to below 1.0.
Rafa's requirements.txt includes the line Flask==0.11.1 so upgrading to V1 probably isn't a good idea so I added wekzeug<1.0, re-ran pip install -r requirements.txt...
Thank you so much for this. I have been a bit away from this repo as it was "just working", but recently had to do a reinstall and found this issue.
It's great to see the community helping out and reporting back so that everyone can benefit from their fixes.
Thanks again! I have added the fix to the repo, so future downloads will not need to implement this solution.
Best regards,
Rafa.
|
