* Restored VT100 function key support
* ESC now clears the entry line
* Spoken commands now become part of the history
* Enhanced help screen with auto word-wrap
* Bugfix: "Show meter" setting didn't persist, now it does
Add 'venv-activate.sh' script
This script in the root makes it easier for devs to discover the
virtual environment which Mycroft should run under. Virtual
environments are new to many, so the commands aren't obvious even
if they are only one liners.
==== Documentation Notes ====
Should probably be mentioned in the Getting Started docs for
Github users. This mirrors the 'mycroft-venv-activate' alias found
under Mark 1/Picroft.
This fixes a stray lock.release() causing a silent
RuntimeError: release unlocked lock
after TTS execution but just before reporting the timing for the TTS system.
* Fix startup scripts
- change start.sh to the new start-mycroft.sh
- fix startup of messagebus service
- fix startup of enclosure
* Fix running dev_setup.sh as root
Use --allow-root when calling dev_setup.sh
* Correct default directory for user
On the Mark-1 the script would create the mycroft-core repo in /home/root instead of /root when running the script as root
* Skip mimic installation correctly
* Allow doing the github install without root
Running mycroft under root stumbles into issues accessing the audio. allowing unstall under pi user is also more intuitive.
* Change ownership of the webcache
* fix starting/stopping wifi-service
* Fix switching permissions
* Correct startup order
- load messagebus before enclosure
- reboot to workaround audio input issue
* Disable updates when switched to github install
* Fix identity update
identity updates weren't transfered back to the mycroft user since the linked file was overwritten. Now the identity folder is linked instead.
* Handle stop correctly in the audio service.
This allows for example the news skill playback to be stopped without
the listening being triggered.
* Handle case where service stops at end of playlist
- Fix issue when receiving multiple stop signals
- Stop method of services now returns True or False depending on if audio was playing
When running on a platform for which there was not DEFAULT.platform
file in the mycroft-skills repo, the downloading of skills would
crash. Now an informational message is shown and the DEFAULT
skills alone are loaded.
The Mark 1 button press can now be "consumed" when a skill handles
the Stop command. When this happens, the button press will not
trigger listening mode. An additional press would be needed to
trigger listening.
This introduces the "mycroft.stop.handled" messagebus message. It
carries a data field called "by" which identifies who handled it.
Currently the values are "TTS" for when speaking ends or the name
of a skill which implements Stop and returns True from the call.
Also fixed a potential bug when the flag to clear queued visemes
was left set after a button press.
* Restore extractdatetime to return False
- Restore extractdatetime to return False if no time was found
- Add tests to make sure this is true
- Add a extract_datetime function to keep coherency with the rest of the functions. (the old extractdatetime still exists for compatibility)
- Update documentation to match
* Minor corrections to docstrings.
* Update format for skill listing
Now send the skills with id and active status
* Add commands to activate/deactivate skills
* Add "unload all except one" functionallity
* Update after rebasing
- fix identifying skills
* Unload skills if they're removed from disk
* Rename _shutdown to default_shutdown
The method is not intended to be non-public, and this should shut up
codacy bot.
* Handle keep command without argument
* Add new commands to help
- Split help into multiple pages as needed
* Support :activate all
Padatious upgrade brings in nested parentheses support and slightly optimized network inputs
Msm upgrade brings in a bugfix for git repos with private or invalid remotes
Security researcher w00t pointed out a potential exploit if an user
starts the Mycroft messagebus service on a system with an exposed
network connection with no protection for port 8181. For now the
start-mycroft.sh script will simply display a CAUTION to point out
this concern and remind them to protect themselves with a firewall.
Future versions of the websocket implementation will use encryption
and authentication.
Steve Penrod
Åke
JarbasAI
devs-mycroft
Matthew Scholefield
Michael Nguyen
Aditya Mehra
Carsten Agerskov
Josh Cox
jarbasal
f-e-l-i-x
Michael P. Scherer