Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix pandora #57

Open
wants to merge 65 commits into
base: master
Choose a base branch
from
Open

Fix pandora #57

wants to merge 65 commits into from

Conversation

ken-mycroft
Copy link

Corrects bad shutdown behavior which caused entire system to lose audio out.

forslund and others added 30 commits August 29, 2018 20:06
The framework is implemented in the Playback Control  skill (https://github.com/mycroftai/skill-playback-control)
For now, the same common_play_skill.py will live in several independent
skills with the same content.
Updated translations: ['sv-se', 'ru-ru']
Fixes broken icon-link in Readme
Updated translations: ['sv-se', 'de-de', 'ru-ru', 'es-es']
Updated translations: ['sv-se', 'de-de', 'ru-ru']
This checks if the reason for pianobar erroring is actually an invalid username and password by simulating the login api on the website
For users that need to manually install pianobar, its helpful to have it fail so that it will notify them they need to perform a manual step first
Fail if requirements.sh doesn't find pianobar
Verify username and passsword doesn't work before erroring
* Removed the explicit (untranslated) removal of "on", "pandora" and "play" in
  _extract_station().  They are already removed by the vocab removal.  Also
  eliminated the removal of "to" as this seemed arbitrary.
* Boosted the score of just "play Pandora" to MULTI_KEY.  It was being caught
  by Spotify instead -- presumably because it was matching on some song with
  "Pandora" in the title.
* Better handling of missing Pianobar "info" file
Check if the Pandora process remains valid after launching.  If the
username/password is incorrect, the pianobar process will self destruct.
Also enhanced the error message spoken in this case.
Allow installs on systems without pkcon
The lsb_release approach failed on the skill tester.
Boneheaded bug in the requirements.sh script meant that systems with
pkcon would not define the list of dependencies to install, so nothing
would be installed.
It wasn't always clear what service is being used with Common Play.
This clarifies it.
forslund and others added 28 commits September 2, 2019 14:18
Odd merge conflict with #30. Same fix here from @krisgesling
Fixes bug where station number is spoken
Removed deprecated values from Skills settingsmeta.json (reported in issue #1092).
Remove deprecated values (name, color)
Information on currently and recently played items was being stored
in the Skill settings causing the settings to stop syncing on
mycroft-core v20.8.1.

This moves all values that are not Skill settings to a local json
database stored in the Skills namespaced filesystem.
Fix settings won't sync on core v20.8.1
The previous requirements.sh script was created prior to Mycroft
performing package installs on multiple systems.

This is now handled by Pako which supports more packaging systems.
Switch dependency definitions to manifest.yml
@krisgesling
Copy link

This was opened against the wrong repo. Have replicated against the Mycroft fork, see above.

This PR can be closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants