When running controls, the expiry of the context used to run a query causing issues creating transactions, and seems to clear the session data

[binaek]

A couple of people have reported different symptoms

1. after the context expires, we are unable to create a transaction

  | | 
  | ERROR: context deadline exceeded
  | 
  + 4 Enable S3 protection in GuardDuty to detect suspicious activities .........................................................................................................  1 /  1 [=     ]
  | | 
  | ERROR: error creating transaction - please restart Steampipe```

This suggests the database connection is blocked for come reason - prehaps and FDW crash/freeze

2) after the context expires, the session data is cleared meaning prepared statements cannot by found

[kaidaguerre]

[kaidaguerre]

To do:

• Investigate why session data is cleared
• Look into mechanism to ensure session data exists on a connection
• Reinstate the RefreshClient functionality to create a new client when we fail to create a transaction. This was removed due to the session data issue