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.

Sign up for GitHub

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

Jump to bottom

Incorrect peer type is sometimes saved in portal database #304

Closed
tulir opened this issue Mar 26, 2019 · 1 comment
Closed

Incorrect peer type is sometimes saved in portal database #304

tulir opened this issue Mar 26, 2019 · 1 comment
Labels
bug: defect Something isn't working and it never has worked
Milestone
0.7.0

Comments

@tulir
Copy link
Member

tulir commented Mar 26, 2019

In some cases, the bridge will create a portal object with an incorrect peer type for some reason (chat instead of channel). Such bridges won't work at all, since many requests (like send message) are peer type specific. The type is then saved into the database and can't be fixed without manually editing the database. This might only be a problem for puppeted accounts.
@tulir tulir added the bug: defect Something isn't working and it never has worked label Mar 26, 2019
@tulir tulir added this to the 0.6.0 milestone Mar 26, 2019
tulir added a commit that referenced this issue May 15, 2019
@tulir
Save peer type when upgrading
8689d0e 
Might have been the cause of #304
@tulir tulir modified the milestones: 0.6.0, soon™ Jul 8, 2019
@tulir tulir mentioned this issue Aug 6, 2019
Merged
@tulir
Copy link
Member Author

tulir commented Aug 7, 2019

This might be related to joining channels via username url (!tg join t.me/username)

@tulir tulir closed this as completed in 6cb8e00 Oct 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug: defect Something isn't working and it never has worked
Milestone
0.7.0
Development

No branches or pull requests
1 participant
@tulir