-
-
Notifications
You must be signed in to change notification settings - Fork 559
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
issue on second run #2
Labels
help wanted
Extra attention is needed
Comments
Make sure you've copied the included |
It's there and in the right directory 🤔 |
jcs @ ~/chatgpt-telegram-Darwin-arm64 % ls -al
total 15728
drwx------@ 7 joshstein staff 224 Dec 4 01:45 .
drwxr-x---+ 66 joshstein staff 2112 Dec 4 01:46 ..
-rw-r--r--@ 1 joshstein staff 85 Dec 4 01:45 .env
-rw-r--r-- 1 joshstein staff 1069 Dec 3 23:55 LICENSE
-rw-r--r-- 1 joshstein staff 742 Dec 3 23:55 README.md
-rwxr-xr-x@ 1 joshstein staff 8035394 Dec 3 23:55 chatgpt-telegram
-rw-r--r-- 1 joshstein staff 29 Dec 3 23:55 env.example
jcs @ ~/chatgpt-telegram-Darwin-arm64 % cat .env
TELEGRAM_ID=<my-telegram-ID>
TELEGRAM_TOKEN=<my-bot-token> and the error is still: /Users/joshstein/chatgpt-telegram-Darwin-arm64/chatgpt-telegram ; exit;
jcs @ ~ % /Users/joshstein/chatgpt-telegram-Darwin-arm64/chatgpt-telegram ; exit;
2022/12/04 01:48:41 Started ChatGPT
2022/12/04 01:48:41 Couldn't load .env file: open .env: no such file or directory
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
[Process completed] and jcs @ ~ % sudo /Users/joshstein/chatgpt-telegram-Darwin-arm64/chatgpt-telegram
Password:
2022/12/04 01:52:23 Started ChatGPT
2022/12/04 01:52:23 Couldn't load .env file: open .env: no such file or directory |
hmm, that's very weird, works fine for me 🤔 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The first time I ran on M2 Mac, binary ran fine and I was able to log in on Chromium. After I logged in it closed out. I DMd the bot, but it did not successfully reply.
I ran the process over again, with a new bot, and then ran into this error.
What would you advise? Thank you for building this useful tool!
The text was updated successfully, but these errors were encountered: