Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Mar 06 21:10
    Sispheor closed #578
  • Mar 06 21:10
    Sispheor commented #578
  • Mar 06 21:09
    Sispheor closed #664
  • Mar 06 21:09
    Sispheor commented #664
  • Mar 06 21:09
    Sispheor closed #665
  • Mar 06 21:09
    Sispheor commented #665
  • Mar 06 21:08
    Sispheor closed #672
  • Mar 06 21:08
    Sispheor commented #672
  • Mar 06 21:08
    Sispheor closed #673
  • Mar 06 21:08
    Sispheor commented #673
  • Mar 06 20:24

    Sispheor on dev

    (compare)

  • Mar 06 20:23

    Sispheor on python39

    (compare)

  • Mar 06 20:23

    Sispheor on v0.7.2

    (compare)

  • Mar 06 20:23

    Sispheor on gh-pages

    Deployed 6458905 with MkDocs ve… (compare)

  • Mar 06 20:22

    Sispheor on master

    [Doc] Fix doc installation on R… [Doc] Add a note to doc: not-co… [Fix] Fix error when trying to … and 12 more (compare)

  • Mar 06 20:22
    Sispheor closed #675
  • Mar 06 20:18
    Sispheor opened #675
  • Mar 06 20:18

    Sispheor on dev

    [Fix] Fix lifo testing. Assert … Fix python 3.9 install on 32 bi… switch CI to Github action (compare)

  • Mar 06 20:17

    Sispheor on python39

    switch CI to Github action (compare)

  • Mar 06 20:11

    Sispheor on python39

    switch CI to Github action (compare)

Nicolas Marcq
@Sispheor
I have to go. I'll retry this evening
Patrick
@corus87
did you try to use your current binary with snowboy?
Nicolas Marcq
@Sispheor
at least the 32 bit version is ok
I pushed the fix for the script
Patrick
@corus87
Perfect, I will try it. I would may try to create a arch64 folder in snowboy and try with the current binary for python39 as on snowboy page it written arch64 is supported, so maybe you don't need to compile a 64 bit version...
Nicolas Marcq
@Sispheor
I tried to use the arm7
it failled
I pushed the pico install order update
you can try with the last version it's should be fine
Patrick
@corus87
alright
Patrick
@corus87
@Sispheor the requirements weren't installed, the issue was the pip install function we implemented some months ago, I removed the lines and added the requirements back to setup.py, this worked. But (and I have no idea why you didn't had the error...) I had the error with crypto.. again, fix was to install cargo.
after fixing everything I installed a fresh raspbian again and used my branch, and this time it worked without errors. I'm going to make PR now
Nicolas Marcq
@Sispheor
?
on a fresh rpi the install was ok with all requirements
from the branch python39
I stop trying to get arch64 working
I'll install 32 bit raspbian and try the script from scratch
the def required worked for me
Patrick
@corus87
This can't be... On a fresh OS? For me almost all requirements were missing...
Nicolas Marcq
@Sispheor
almost all? It cannot be almost
it's all or nothing
but only some would be weird
also I didn't need cargo
but all of this was on 64 bit OS
I'll try with the 32 bit
Patrick
@corus87
Almost because I guess some other libs were installed by some apt packages like werkzeug was not missing
But sure, try it, I will be damned if it will work on your side ^^
Nicolas Marcq
@Sispheor
we'll see that :)
Patrick
@corus87

any updates on your side @Sispheor ? I've installed raspberry os again and run the script, well what should I say...

Installing Kalliope... This can take up to 15 minutes...
Branch 'python39' set up to track remote branch 'python39' from 'origin'.
Switched to a new branch 'python39'
Processing /home/pi/kalliope
  Preparing metadata (setup.py) ... done
Building wheels for collected packages: kalliope
  Building wheel for kalliope (setup.py) ... done
  Created wheel for kalliope: filename=kalliope-0.7.1-py3-none-any.whl size=4434363 sha256=a153ff8c7d8aab8e9a568b8363d4f67f746f120605f3e3a833465f0e3e91a897
  Stored in directory: /tmp/pip-ephem-wheel-cache-w8r0b7es/wheels/5d/60/b3/d26ece7cf49680bce26dfce35f07e0ff13ba3889bc894eefba
Successfully built kalliope
Installing collected packages: kalliope
Successfully installed kalliope-0.7.1
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Installing Kalliope...[OK]
Adding default-server to /etc/pulse/client.conf..[OK]
Adding 'autospawn = no' to /etc/pulse/client.conf..[OK]
Adding user pi to group pulse-access
Adding 'load-module module-alsa-sink device=hw:0,0' to /etc/pulse/system.pa..[OK]
Adding 'set-default-sink alsa_output.hw_0_0' to /etc/pulse/system.pa..[OK]
Create pulseaudio service
Creating pulseaudio service..[OK]
Created symlink /etc/systemd/system/multi-user.target.wants/pulseaudio.service → /etc/systemd/system/pulseaudio.service.
Enable and starting pulseaudio.service..[OK]
Installing pulseaudio service..[OK]

pi@raspberrypi:~/kalliope_starter_de $ kalliope start
Traceback (most recent call last):
  File "/usr/local/bin/kalliope", line 5, in <module>
    from kalliope import main
  File "/usr/local/lib/python3.9/dist-packages/kalliope/__init__.py", line 8, in <module>
    from kalliope.core import Utils
  File "/usr/local/lib/python3.9/dist-packages/kalliope/core/__init__.py", line 1, in <module>
    from kalliope.core.OrderAnalyser import OrderAnalyser
  File "/usr/local/lib/python3.9/dist-packages/kalliope/core/OrderAnalyser.py", line 5, in <module>
    import yaml
ModuleNotFoundError: No module named 'yaml'
pi@raspberrypi:~/kalliope_starter_de $ python3
Python 3.9.2 (default, Mar 12 2021, 04:06:34) 
[GCC 10.2.1 20210110] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import yaml
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'yaml'
>>> import six
>>> import SpeechRecognition
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'SpeechRecognition'
>>> import jinja2
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'jinja2'
>>> import cffi
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'cffi'
>>> import gevent
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'gevent'
>>> import gTTS
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'gTTS'

Please tell me you have the same error ^^

Nicolas Marcq
@Sispheor
yes I tested
inddeed all lib are not installed
Patrick
@corus87
okay good to hear... Yeah adding back the requirements to setup.py as in my PR fixed it for me
Nicolas Marcq
@Sispheor
I merged your PR
I'm installing
I think I'll just add the -v flag
so the user can sse that the install is progressing
Patrick
@corus87
Yeah maybe better, also for debugging when something went wrong
Nicolas Marcq
@Sispheor
all good
I think it's time to swich the CI to Github action
just the time to do that and I do the release
Patrick
@corus87
on my side it all went good too with the latest commits
sounds good
and I will try to get a rpi 4 soon, so I can built a 64 bit lib for snowboy. Just hard to get pi4 lately...
Nicolas Marcq
@Sispheor
yep... like graphic cards and all other electronic stuff
Nicolas Marcq
@Sispheor
kalliope 0.7.2 released !
thanks @corus87 for your help on this one
Patrick
@corus87
No problem, always a pleasure. Thanks for the release
blackwing12344
@blackwing12344
ok so, I've been trying to set up a server on google's server thing, and I've successfully installed Kalliope onto Debian Bullseye. When I try to do the audio test, it doesn't even say that there is no mic connected or anything, it says the rec command doesn't exist. I've been working with someone who develops on Linux professionally because I have never used Linux or servers in my life and that's the only way I have been able to get this far. So what the hell do I do now?
ive also currently got it installed on a vm on my home machine, and it gives me the same problem
Nicolas Marcq
@Sispheor
Start to buy an Alexa. Then learn to talk politly to people when you join an open source community. And then come back here.