name: myna-funasr
description: FunASR SenseVoice-Small speech-to-text inference snap for Myna
snapcraft: https://github.com/canonical/myna/blob/main/funasr-snap/snap/snapcraft.yaml
upstream: https://github.com/canonical/myna
upstream-relation: the publisher is the upstream (Canonical); this snap is built from that repository
plugs:
hardware-observe:
request-type: auto-connection
reasoning: |
modelctl (the `funasr` CLI and the install and post-refresh hooks)
probes local hardware via /sys/bus/**, /sys/devices/system/cpu/** and
/sys/class/drm/** for list-engines, show-engine and status. Without
the plug, list-engines exits non-zero on /sys/bus/usb/devices. Myna
Settings (the desktop configuration app) calls list-engines to report
the installed backend, so every store install would show a broken
diagnostics page until the user connected the plug by hand.
Read-only: no device node is opened and nothing is written.
system-observe:
request-type: auto-connection
reasoning: |
Plugged by the server daemon for memory-pressure monitoring, which
we will need: the shared Myna server reads PSI from
/proc/pressure/memory to warn the user when decoding is being slowed
by memory reclaim. myna-parakeet already runs this monitor under the
same grant; myna-funasr will adopt it. Read-only.
This request has been added to the queue for review by the @reviewers team.
Hello @charles05 
Both requests are reasonable and consistent with the existing Myna snap family. Hence, this is a +1 for auto-connection of both hardware-observe and system-observe to myna-funasr.
1 Like
Gentle ping for a second +1 to get FunASR fully operational
Pinging for the second review.
Hello @charles05,
My apologies for the delay here! This is a +1 from me as well for granting auto-connect for the hardware-observe and system-observe interfaces for snap myna-funasr
1 Like
+2 votes for, 0 against, granting auto-connection of both hardware-observe and system-observe to myna-funasr.
This is now live!