fix: Exception Handling (#141)

Passes the actual exception (rather than relying on `sys.exc_info()` which can fail due to race conditions in multithreaded and async code.

cloudquery/sdk/scheduler/scheduler.py

@@ -108,13 +108,13 @@ def resolve_table(
                     resource = self.resolve_resource(
                         resolver, client, parent_item, item
                     )
-                except Exception:
+                except Exception as e:
                     self._logger.error(
                         "failed to resolve resource",
                         client_id=client.id(),
                         table=resolver.table.name,
                         depth=depth,
-                        exc_info=True,
+                        exc_info=e,
                     )
                     continue
                 res.put(SyncInsertMessage(resource.to_arrow_record()))
@@ -145,14 +145,14 @@ def resolve_table(
                     resources=total_resources,
                     depth=depth,
                 )
-        except Exception:
+        except Exception as e:
             self._logger.error(
                 "table resolver finished with error",
                 client_id=client.id(),
                 table=resolver.table.name,
                 resources=total_resources,
                 depth=depth,
-                exc_info=True,
+                exc_info=e,
             )
         finally:
             res.put(TableResolverFinished())