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

Long-polling request failed: Request connection error: Response payload is not completed #9

Open
MurzNN opened this issue Aug 16, 2017 · 5 comments

Comments

@MurzNN
Copy link

MurzNN commented Aug 16, 2017

After some days of work - matrix-puppet-hangouts bridge show the errors in logs:

10:08
WARNING:hangups.channel:Long-polling request failed: Request connection error: Response payload is not completed
10:08
WARNING:hangups.channel:retry attempt count is now 1
10:08
WARNING:hangups.channel:Long-polling request failed: SID became invalid
10:08
WARNING:hangups.channel:retry attempt count is now 2

After this - when I try to send message - it show error:

16:16
Message send failure! Exception: Session is closed

Restarting bridge solve the problem. Can I fix this problem without full restarting of puppet?

@AndrewJDR
Copy link
Collaborator

What version of hangups are you using?

@MurzNN
Copy link
Author

MurzNN commented Aug 17, 2017

hangups (0.4.3)

@AndrewJDR
Copy link
Collaborator

AndrewJDR commented Aug 17, 2017

Ah ok, I fixed a similar issue with retries within hangups, but it should be in there if you have 0.4.3.
I'm really not sure what the problem is unfortunately. I've had a hangups bridge running for quite some time (months) without any issues.
It does look like something failed inside the retry logic of hangups, if I had to guess. You can see if @tdryer and the folks over at the hangups project have any ideas.

@AndrewJDR
Copy link
Collaborator

You could also try running the latest git version of hangups instead of the tagged one to see if they fixed an issue recently. To do that, you can follow the instructions I left in this thread:
#7

@AndrewJDR
Copy link
Collaborator

Another option you have is to run the same exact commit of hangups that I have been running on my bridge, which is:
30ba087bd5b99da98e463c1b03405c06eeaad519
Run git reset --keep 30ba087bd5b99da98e463c1b03405c06eeaad519 inside your hangups repo to reset to that.

Maybe some bug was introduced recently (sometime between that commit but before 0.4.3) into hangups, and that would help you identify whether that was the case.

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