Skip to content

Commit 2a5996b

Browse files
authored
fix: Fix exception logging (#18)
It's `exc_info` not `exec_info`, and `exc_info` just needs to evaluate to True. It takes the exception from the context.
1 parent a1b07e8 commit 2a5996b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

cloudquery/sdk/scheduler/scheduler.py

+2-2
Original file line numberDiff line numberDiff line change
@@ -110,7 +110,7 @@ def resolve_table(
110110
"failed to resolve resource",
111111
table=resolver.table.name,
112112
depth=depth,
113-
exception=e,
113+
exc_info=True,
114114
)
115115
continue
116116
res.put(SyncInsertMessage(resource.to_arrow_record()))
@@ -142,7 +142,7 @@ def resolve_table(
142142
"table resolver finished with error",
143143
table=resolver.table.name,
144144
depth=depth,
145-
exec_info=e,
145+
exc_info=True,
146146
)
147147
finally:
148148
res.put(TableResolverStarted(count=table_resolvers_started))

0 commit comments

Comments
 (0)