-
Notifications
You must be signed in to change notification settings - Fork 14
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 gosmee bufio.Scanner: token too long
#77
Comments
that's weird one! was there any way to reproduce it ? |
I am not sure how to reproduce this problem yet. I'd be great to have logs from the |
Okay, was able to reproduce it. It has to do with really large payloads. I made a commit with a huge commit message and I ran into that error. |
I have referenced my test CI job that cause the problem here. |
See r3labs/sse#158, "Improve receive message error handling." Fixes chmouel#77, "`ERROR gosmee bufio.Scanner: token too long`".
See r3labs/sse#158, "Improve receive message error handling." Fixes chmouel#77, "`ERROR gosmee bufio.Scanner: token too long`".
See r3labs/sse#158, "Improve receive message error handling." Fixes chmouel#77, "`ERROR gosmee bufio.Scanner: token too long`".
See r3labs/sse#158, "Improve receive message error handling." Fixes chmouel#77, "`ERROR gosmee bufio.Scanner: token too long`".
Saw the following error that killed the
gosmee client
process:The text was updated successfully, but these errors were encountered: