All Pull Requests

[HassanAfnan]

Let's talk about this issue # OSError: [Errno 86] Bad CPU type in executable: #125

I have seen the tts.py file and there is an issue of path that is saved in this variable PIPER_URL i have edit this file and fixed some issues and i have commented your code and add my code where the piper issue is solved and don't forget when you are running the project locally by running this command "poetry run 01 --local" then insure you have run this command "cargo build --release"
under the directory where cargo.lock and cargo.toml it will compiling the packages like this

(01os-py3.10) threeconst@ThreeConst:~/Desktop/3Const/afnan-work/software/source/server/services/stt/local-whisper/whisper-rust$ cargo build --release
Compiling proc-macro2 v1.0.78
Compiling unicode-ident v1.0.12
Compiling libc v0.2.153
Compiling glob v0.3.1
Compiling prettyplease v0.2.16
Compiling rustix v0.38.31
Compiling clang-sys v1.7.0
Compiling memchr v2.7.1
Compiling quote v1.0.35
Compiling syn v2.0.48
Compiling minimal-lexical v0.2.1
Compiling regex-syntax v0.8.2
Compiling cfg-if v1.0.0
Compiling linux-raw-sys v0.4.13
Compiling bitflags v2.4.2
Compiling libloading v0.8.1
Compiling nom v7.1.3
Compiling regex-automata v0.4.5
Compiling home v0.5.9
Compiling either v1.9.0
Compiling bindgen v0.69.2
Compiling which v4.4.2
Compiling regex v1.10.3
Compiling cexpr v0.6.0
Compiling cc v1.0.83
Compiling rustc-hash v1.1.0
Compiling autocfg v1.1.0
Compiling lazy_static v1.4.0
Compiling shlex v1.3.0
Compiling pkg-config v0.3.29
Compiling log v0.4.20
Compiling lazycell v1.3.0
Compiling peeking_take_while v0.1.2
Compiling lock_api v0.4.11
Compiling cmake v0.1.50
Compiling alsa-sys v0.3.1
Compiling utf8parse v0.2.1
Compiling fs_extra v1.3.0
Compiling parking_lot_core v0.9.9
Compiling anstyle-parse v0.2.3
Compiling colorchoice v1.0.0
Compiling scopeguard v1.2.0
Compiling smallvec v1.13.1
Compiling bitflags v1.3.2
Compiling anstyle v1.0.5
Compiling anstyle-query v1.0.2
Compiling anstream v0.6.11
Compiling nix v0.24.3
Compiling heck v0.4.1
Compiling anyhow v1.0.79
Compiling strsim v0.10.0
Compiling clap_lex v0.6.0
Compiling cpal v0.15.2
Compiling clap_builder v4.4.18
Compiling clap_derive v4.4.7
Compiling alsa v0.7.1
Compiling parking_lot v0.12.1
Compiling dasp_sample v0.11.0
Compiling clap v4.4.18
Compiling hound v3.5.1
Compiling whisper-rs-sys v0.8.0
Compiling whisper-rs v0.10.0
Compiling whisper-rust v0.1.0 (/home/threeconst/Desktop/3Const/afnan-work/software/source/server/services/stt/local-whisper/whisper-rust)
Finished release [optimized] target(s) in 1m 51s

it will set up whisper-rust in you system then run this command "poetry run 01 --local" then it will start recording and giving you answer.

And one thing if you running locally you have to download one of this library
Ollama
LM Studio

after installed this library you should have to install it's models

and these steps you will find easily in the Ollama dashboard or LM Studio.

lets talk about this issue # cant install pip simpleaudio #114

you don't have to install this package with pip just go to the directory where the poetry is and open the shell by running this command "poetry shell" after opened the shell simply run the command "poetry install" it will install all the packages including this "simpleaudio" also.

Let's talk about this issue # Update link to Piper download #100 HassanAfnan#2.

When you run this command "poetry run 01 --local" under the software directory it will giving you this error "asset_ur referenced before assignment" i have commented your code and added my code with the solution of the above piper download error.

Let's talk about this issue # Not running on !Ubuntu Linux #103

install this package sudo apt-get install portaudio19-dev ffmpeg cmake
and make sure you have export the OPENAI_API_KEY and successfully installed all the packages from poerty.lock and save the ngrok token in ngrok.yml file by running this command "ngrok authtoken your auth token"

it will run the project successfully on !Ubuntu Linux.

[dheavy]

Hey @HassanAfnan 👋🏾 , just a few simple best practice rules when contributing to an open source (or even closed source) project.

(Disclaimer: I'm not a maintainer for the project, merely a contributor like yourself 🙂)

1. Make sure you tackle one issue per PR. Sometimes a single PR can close several issues if they have the same root cause, but a single PR should not try to tackle different root cause at once. Every code change is a potential regression, so you want to keep changes as specific as possible to make future disabling, editing and investigation as fast as possible 🔍 (see this interesting blog post for details).

2. Make sure you work on the latest version of the code before submitting a PR. Otherwise you'd be working on issues that already be resolved and merged, or you will have conflicts in your branch (see Github's message on top above this comment). Sadly, conflicting branches cannot be merged into a code base. 💔

3. PR should focus on code. You have provided excellent information on several subjects. Unfortunately, the people will not benefit from it because it is not code that can be merged into the main code base for their perusal, and most users will not come find it here. I strongly encourage you to share those information in the Discord or as a comment in the issue you have mentioned as well! ℹ️

4. Please replace code, avoid commenting. It's good hygiene to actually replace someone else's code rather than comment it. This is part of the Clean Code methodology and makes the code more readable. It also helps verify what is actually changing when comparing the code version in Git. ✨

This will make life easier for whoever takes the time to review the contribution. Looking forward to contribute in this project and others with you!