Debian Patches
Status for locust/2.46.7-1
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| increase-subprocess-timeout.patch | increase the join timeout of test subprocesses Raise the default from 1 to 5 seconds, and the 3 seconds that test_processes_separate_worker passes to 10: its timeout starts when the worker process is spawned, so it covers the startup, the master's run and the shutdown of the 4 child workers. The arch:all build of 2.46.6-3 failed on the buildd with "Process took more than 3 seconds to terminate". |
Sandro Tosi <morph@debian.org> | not-needed | 2026-10-17 | ||
| wheel-anchor-include-patterns.patch | anchor wheel include/exclude patterns to the project root The unanchored "locust" include also matches the webui/locust/ directory unpacked from the webui component tarball, and the wheel would ship the web UI sources, node tooling and tests. Anchor the patterns and exclude what upstream's own sdist excludes, so the wheel matches the one on PyPI. |
Sandro Tosi <morph@debian.org> | not-needed | 2026-09-24 | ||
| relax-configargparse-requirement.patch | accept configargparse 1.7 The only runtime changes in configargparse 1.7.1 are for Python < 3.9, for pathlib entries in default_config_files, and for parsers created with exit_on_error=False; locust uses none of them, so 1.7 (in Debian) is enough. |
Sandro Tosi <morph@debian.org> | not-needed | 2026-09-24 | ||
| geventhttpclient-2.6-max-redirect-test.patch | expect the 302 response in test_max_redirect_setting geventhttpclient 2.6 no longer follows redirects when max_redirects is 0: it returns the 3xx response instead of raising RetriesExceeded, and locust counts it as a success. Expect the 302 response, with no failure and no request to the redirect target; the test now needs geventhttpclient 2.6. . This combines two upstream commits; the second one only adds a mypy "type: ignore" comment. |
Lars Holmberg <lars.holmberg@redshirt.se> | no | upstream, https://github.com/locustio/locust/commit/6ae4c1f3f89a3230224dd011f2a58568379da200, https://github.com/locustio/locust/commit/0c1cfa85a963245d6ca5ef17ed34c8e0f8105447 | 2026-10-17 | |
| PR3541-percent-encode-request-target.patch | percent-encode the request target in FastHttpUser LocustUserAgent._urlopen() sends url_split.request_uri as it is, while geventhttpclient's own UserAgent sends the percent-encoded quoted_uri. geventhttpclient 2.6 validates the request target and raises a ValueError on a space in the path or query before any request event fires, so the request is missing from the statistics. Send quoted_uri, falling back to request_uri on geventhttpclient older than 2.3.4, which doesn't have it. |
Suliman Abdulrazzaq <suliman9000a@gmail.com> | yes | upstream, https://github.com/locustio/locust/pull/3541 | 2026-10-17 | |
| PR3549-report-malformed-response-as-failure.patch | report a malformed HTTP response in FastHttpUser as a failed request When geventhttpclient cannot parse the status line or the headers of a response (--host pointing at a TLS, HTTP/2 or Redis port, or a server closing the connection in the middle of the headers), HTTPParseError is raised out of FastHttpSession.request(): no request event fires, so the request is missing from the statistics, and a catch_response block never runs. Add HTTPParseError to FAILURE_EXCEPTIONS, so the error is reported as a failed request with status code 0, like the other connection errors. |
Suliman Abdulrazzaq <suliman9000a@gmail.com> | yes | upstream, https://github.com/locustio/locust/pull/3549 | 2026-10-17 |