`durable` fails pytest tests without a database

[samueljsb]

When when using pytest-django, tests must be allow-listed to access a database. get_transaction_state (and its users, like durable) fails if run in tests that are not allowed to access the database (because they are not using the django_db marker or fixture) if there were other tests in the same process that had opened connections to the database.

Note

We addressed this at Kraken internally in https://github.com/octoenergy/kraken-core/commit/a4546fe4de9902e651da030992e8c2ecdc1e9d95, which didn't merge before this project was extracted.

[meshy]

Do you have any recommendations as to how to reproduce this?

I tried the following, but wasn't able to reproduce the error:

diff --git tests/test_db.py tests/test_db.py
index 6136f9c..1684b46 100644
--- tests/test_db.py
+++ tests/test_db.py
@@ -574,6 +574,13 @@ class TestDurable:
         # The transaction has been rolled back.
         assert db.in_transaction(using=db_name) is False

+    @pytest.mark.django_db(databases=[])
+    def test_not_allowed_db_access(self) -> None:
+        """
+        Tests which aren't allowed access to a DB cannot have a transaction open on it.
+        """
+        assert _durable_example() is True
+

 class TestRunAfterCommit:
     """