-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Reopen #3208 #3268
Comments
Hi, I'm GitMate.io! It seems you've just enabled the issue triaging. I'm just scraping all issues from your repository and will give you some more information about this in a few minutes or so. Because of the rate limit we can't scrape all information (including all comments and authors) right now - our system is already set up to scrape this in the next days over which the predictions will become more precise every day. If you want me to use a different account for triaging your issues, simply create one and log in with it. Sit tight! |
@asvetlov ??? |
@kxepal I've enabled GitMate.io bot. |
@Swamp-Ig the referenced issue has a long conversation, I still don't get your problem. Could you summarize the problem and your finding? |
Ok. I almost feared that you had being hacked to spead some ad (: |
OK the issue is that if you do a HTTP put to my device, the TCP connection goes crazy and the request fails. The same thing doesn't happen if you use standard non async requests lib. I've re-coded my library now to just use requests anyhow, since aiohttp won't work. |
I'm sorry but "goes crazy" is not a technical language. |
I figured out the issue. The device I was connected to couldn't handle fragmented requests. Will close. |
I'm not sure what's happened exactly, but #3208 still seems to be happening for me.
It did work at one point. Not sure what changed exactly.
The text was updated successfully, but these errors were encountered: