Introduce **kwargs to request_success/failure parameter list

[karol-brejna-i]

Fixes #745

[codecov]

Codecov Report

Merging #746 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #746   +/-   ##
=======================================
  Coverage   65.93%   65.93%           
=======================================
  Files          14       14           
  Lines        1374     1374           
  Branches      214      214           
=======================================
  Hits          906      906           
  Misses        421      421           
  Partials       47       47

Impacted Files	Coverage Δ
locust/stats.py	78.35% <100%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 592532b...e91a710. Read the comment docs.

[ovanes]

Can you please explain how this code is supposed to work in distributed Locust scenario: Master + Multiple Slave. How the kwargs are transferred from a slave to the master node.

[karol-brejna-i]

@ovanes Sorry for the late answer.

As described here: #745 - current implementation prevent users from introducing their own (additional) on_request_success/failure. This patch is simply about enabling users to do so, and do whatever they want in the additional handler.

Reporting to master is left to the default handlers.

In this case you have:

• exact the same Locust mechanics for collecting the results,
• ability for the users to capture/handle additional metadata.

I imagine the next step could be to pass the additional args further, but this is something that needs some thinking (locust stats module pluggability to include user's statistics, etc.). This PR doesn't solve all the problems but gives more flexibility to the users.

[heyman]

Thanks for the PR! Sorry for the long wait before merging this.