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

Telegram task send almost all log to chat #5535

Closed
Lntnam opened this issue Sep 18, 2016 · 7 comments
Closed

Telegram task send almost all log to chat #5535

Lntnam opened this issue Sep 18, 2016 · 7 comments

Comments

@Lntnam
Copy link

Lntnam commented Sep 18, 2016

Expected Behavior

Telegram task should only send chat based on subscription

Actual Behavior

Sends everything, almost all log lines.
even after /unsub everything
/showsubs shows nothing

Your FULL config.json (remove your username, password, gmapkey and any other private info)

Just basic Telegram config

Output when issue occurred

Nothing special from log

Steps to Reproduce

Turn on Telegram & set a master ID in config
Start bot

Other Information

Branch:
dev
Git Commit:
1963971
Python Version:
2.7.10

@Gobberwart
Copy link
Contributor

What is an instagram task?

@Gobberwart
Copy link
Contributor

If you mean telegram, this should be fixed in latest dev.

@Lntnam Lntnam changed the title Instagram task send almost all log to chat Telegram task send almost all log to chat Sep 19, 2016
@Lntnam
Copy link
Author

Lntnam commented Sep 19, 2016

@Gobberwart haha I mean telegram. I must be crazy while writing Instagram...

Actually I wrote this after fetching the latest dev...

@Gobberwart
Copy link
Contributor

LOL no worries, in which case, fixed by #5537

@Gobberwart
Copy link
Contributor

If you still have that issue, you might want to try "/showsubs" to see what you're subscribed to and remove something (eg. "/unsub all")

@Lntnam
Copy link
Author

Lntnam commented Sep 19, 2016

Noted, will try dev branch again later.
I had to switch back to master because of this bug.

@Gobberwart
Copy link
Contributor

Worst case scenario - stop bot, delete database file (data/username.db) and start bot again. db will get recreated cleanly.

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