-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Cannot decode 502 #481
Comments
something as simple as
makes it work, so if you are willing to accept a PR let me know |
Thanks for te report. Could you please provide more info on how to reproduce this? |
I suspect this error might have been introduced in #451 and I might know a simple fix, but I'd love to be able to reproduce it so that I can write a test. |
well, my configuration is a ecs instance behind an elb...and i suppose the elb can't keep up therefore it throws 502 |
NVM, I believe managed to reproduce it, and I've pushed a fix. Locust should be able to handle failures and exceptions without crashing. Could you try with the latest master and confirm that it's been fixed? |
sure, just tried and looks fine now, thanks a lot |
Great! Thanks again for reporting. |
Looks like Locust doesn't handle properly 502
I tried to debug it and this is the result of the var
report
here https://github.com/locustio/locust/blob/master/locust/web.py#L154 istherefore fails to json encode the
report['errors'][0]['error']
as not built-in (and w/o a defined encoder i presume)The text was updated successfully, but these errors were encountered: