2.37.0

[cyberw]

What's Changed

• Web UI: Use mutations for state buttons by @andrewbaldwin44 in Web UI: Use mutations for state buttons #3120
• fix error message to be idiomatically correct English by @davidxia in fix error message to be idiomatically correct English #3121
• Add locust exporter import by @andrewbaldwin44 in Add locust exporter import (used in Locust Cloud) #3122
• Update uv to 0.7.2 by @cyberw in Update uv to 0.7.2 #3125
• Add command line option to export json results into a file by @ajt89 in Add command line option to export json results into a file #3124
• Webui: Fix Failing Tests by @andrewbaldwin44 in Webui: Fix Failing Tests #3126

New Contributors

• @davidxia made their first contribution in fix error message to be idiomatically correct English #3121

Full Changelog: 2.36.2...2.37.0

[shirleyqing]

Hi @cyberw, @andrewbaldwin44,

I noticed in the Locust 2.37.0 changelog that there is a new addition for "Add locust exporter import" in PR #3122. Thank you for the update! I have a couple of questions regarding this change:

1. Could you clarify which locust_exporter package is being referred to in this import? I couldn't find a package named locust-exporter on PyPI, and the commonly known locust_exporter (e.g., from Container Solutions at https://github.com/ContainerSolutions/locust_exporter) seems to be a Go-based Prometheus exporter rather than a Python module. Is this import intended for a specific Python package, or is it for a different implementation?
2. Is the locust_exporter import currently being used in the Locust codebase, or is it a preparatory change for future functionality? I see the import in locust/main.py with a try-except block, but I'm curious about its intended usage.

Any details or pointers to documentation would be greatly appreciated! Thanks for your time and contributions to Locust.

[cyberw]

Hi! Locust Exporter is used by locust cloud. It is not a public package/repo, because it provides nothing of use to non-cloud users.

Importing it here is a little awkward, but is needed because it adds command line parameters parameters (same as with locust-cloud c966697#diff-28a4f6f603cec74c03e58235026a0ef520d6a3937cadcc1465edbfea6268f447L33)

In short:

• If you're using Locust Cloud, it will be installed and used automatically on our hosted infrastructure
• If you're not using Locust Cloud, nothing will be imported, and you don't need to care about it.
• It is unrelated to any other similarly named packages :)