Error Logging in FastHttpUser

[cyberw]

Discussed in https://github.com/orgs/locustio/discussions/2936

^{Originally posted by swaalt October 10, 2024}
Hi, I am using FastHttpUser and when I receive a 404 the fail is registered like this, this happens because the geventhttpclient saves in the exception the badstatuscode text the url of the request I made, which is dynamic and appears separated by each one,
I need that either I take the “name” or simply do not place anything, just place the badstatuscode 404, can this be addressed with the locust as it is now or do I have to modify something?

[cyberw]

PR:s welcome (I'll look at it myself, but no guarantees on the timing)

[jayantp2003]

I would like to work on this issue. Please assign me this issue.

[cyberw]

Ideally, make it work the same as HttpUser.

[swaalt]

I made this change to make the URL parameter optional by modifying the repository for geventhttpuser, then modified the use of that class in the Locust repository by removing the use of the url parameter in the "LocustUserAgent" class in fasthttp.py.

geventhttpclient:swaalt/geventhttpclient@94253d4

fasthttp:swaalt@ef4d4c3

[cyberw]

Interesting. But maybe even better/easier to subclass the ConnectionError class (in locust) and override the __repr__ method there? Such a PR would be most welcome!

[swaalt]

Would that be okay?
swaalt@c9192ac

[cyberw]

Looks great! PR it? Maybe add a test case for it? (ignore any other errors, the tests are a bit flaky atm)

[swaalt]

Attach the PR : #2944