Skip to content
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

Error #3

Closed
krackxor opened this issue Oct 1, 2024 · 3 comments
Closed

Error #3

krackxor opened this issue Oct 1, 2024 · 3 comments

Comments

@krackxor
Copy link

krackxor commented Oct 1, 2024

Screenshot_20241001-223513

@FlyingFathead
Copy link
Owner

FlyingFathead commented Oct 1, 2024

That's an odd bug that I'm working on rn -- try disabling the send-as-messages transcripts from config.ini by settingsendasmessages = True to False as a temporary workaround.

It occasionally happens only with longer files that TG tries to parse into messages.

Also, please make sure that you've cloned the newest version that's out just today (v0.17). You can check your version with /about

@FlyingFathead
Copy link
Owner

I've pushed the latest changes to the main branch that aim to fix the issue with an improved exception catching block -- the issue was in Telegram's message length cap that sometimes overflows when longer messages are chunked into sequences, I've now redone the logic for that.

Please pull the latest version (v0.1701) using this command:

git pull origin main

You can also re-clone the repository if that doesn't work for you.

If you still get the error, please re-open another issue with preferably a copypaste from the backend, and I'll look into it.

Thanks and have a nice day!

@krackxor
Copy link
Author

krackxor commented Oct 1, 2024

Tanks bro

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants