Bump gevent from 25.5.1 to 25.9.1

[dependabot]

Bumps gevent from 25.5.1 to 25.9.1.

Commits

• 86937db Preparing release 25.9.1
• f3334b9 Merge pull request #2141 from gevent/update-pypy
• ebe9f21 Update PyPy from 3.10v7.3.17 to 3.11v7.3.20
• 57ea2bc Merge pull request #2140 from gevent/issue2139
• afb63b7 Fix 2139 by typing the ivar correctly.
• 533803f Bump setup-python from 5 to 6
• 51010e4 Merge pull request #2138 from gevent/dependabot/github_actions/github-actions...
• 18168bc Bump actions/checkout from 4 to 5 in the github-actions group
• ca0bc97 Back to development: 25.8.3
• 7dd45df Preparing release 25.8.2
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[BenjaminPelletier]

Note to other reviewers: This change seems to consistently prevent mock_uss tests from completing, so some investigation will be necessary before this PR is merged.

[mickmis]

Note to other reviewers: This change seems to consistently prevent mock_uss tests from completing, so some investigation will be necessary before this PR is merged.

Some first findings:

• The unit tests do complete. The hang seems to happen after they run successfully.
• This also happens when running locally uv run pytest -s -vvv (which is ran within the running container in CI). This seems to indicate the hang does not happen within the mock_uss container running geoawareness.
• When stopping locally with Ctrl+C the hang the following warning is printed:

/home/misbach/.local/share/uv/python/cpython-3.13.5-linux-x86_64-gnu/lib/python3.13/multiprocessing/resource_tracker.py:301: UserWarning: resource_tracker: There appear to be 3 leaked shared_memory objects to clean up at shutdown: {'/psm_756d6aad', '/psm_44a12867', '/psm_8a9ef308'}

[mickmis]

The issue does happen as well with version 25.8.1 of gevent (there is other version between 25.5.1 and 25.8.1).

[mickmis]

The warning is actually also printed with our current version, e.g. in the CI:

/root/.local/share/uv/python/cpython-3.13.5-linux-x86_64-gnu/lib/python3.13/multiprocessing/resource_tracker.py:301: UserWarning: resource_tracker: There appear to be 3 leaked shared_memory objects to clean up at shutdown: {'/psm_db14f18c', '/psm_625fc444', '/psm_69893dfe'}
  warnings.warn(

So that is not introduced by the gevent upgrade. But could still be relevant?

[BenjaminPelletier]

This issue continues to puzzle me. I don't know of anything we have changed that would have impacted the hanging problem discussed on this PR, but the CI on this PR has succeeded the past two times it has been run. I'm inclined to make sure it continues to reliably pass after a few more updates and then go ahead and merge this PR, essentially archiving the discussion on freezing.