From e9729a24c841262813472dce0f19f1516542899d Mon Sep 17 00:00:00 2001 From: Ville Brofeldt Date: Fri, 23 Dec 2022 10:49:59 +0200 Subject: [PATCH] fix a few typos --- superset/db_engine_specs/base.py | 2 +- superset/sql_lab.py | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/superset/db_engine_specs/base.py b/superset/db_engine_specs/base.py index 087918ebf8a3f..43dd6078768aa 100644 --- a/superset/db_engine_specs/base.py +++ b/superset/db_engine_specs/base.py @@ -1598,7 +1598,7 @@ def prepare_cancel_query(cls, query: Query, session: Session) -> None: """ Some databases may acquire the query cancelation id after the query cancelation request has been received. For those cases, the db engine spec - can record the cancelation intent so that the query can be either be stopped + can record the cancelation intent so that the query can either be stopped prior to execution, or canceled once the query id is acquired. """ return None diff --git a/superset/sql_lab.py b/superset/sql_lab.py index 7222c76d1eeb1..143806c7f508f 100644 --- a/superset/sql_lab.py +++ b/superset/sql_lab.py @@ -614,7 +614,7 @@ def cancel_query(query: Query) -> bool: """ Cancel a running query. - Note some engines implicitly handle the cancellation of a query and thus no explicit + Note some engines implicitly handle the cancelation of a query and thus no explicit action is required. :param query: Query to cancel