From 1a36fb17d5d8b8843a95efa9d04de0e395825d37 Mon Sep 17 00:00:00 2001 From: Marcelo Fernandes Date: Thu, 25 Jul 2024 17:18:53 +1200 Subject: [PATCH] fixup! fixup! Introduce timeouts module --- src/django_pg_migration_tools/timeouts.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/django_pg_migration_tools/timeouts.py b/src/django_pg_migration_tools/timeouts.py index b5ee095..c2b7f1f 100644 --- a/src/django_pg_migration_tools/timeouts.py +++ b/src/django_pg_migration_tools/timeouts.py @@ -201,9 +201,9 @@ def apply_timeouts( # # In other cases, such as running a Django migration with # timeouts, it is unhelpful to let the leak carry through, - # because the `distribute_migrate` command will blow up, and if - # the transaction is ABORTED, it means that the migration - # already failed in any case. + # because the `migrate` command will blow up, and if the + # transaction is ABORTED, it means that the migration already + # failed in any case. if close_transaction_leak and not conn.is_usable(): # This will ping the database to verify if the connection # is usable or not.