microsoft/azuredatastudio-postgresql

Scripting fails after system wakesup for postgres objects

sahalMoidu opened this issue · 7 comments

Describe the bug
After the computer sleeps and wakes up, the connection to the postgres server seems to invalid. When trying to script select or create using the context menu scripting failed error occurs

Object of type NoneType does not support script operation ScriptOperation.SELECT

To Reproduce
Steps to reproduce the behavior:

  1. Connect to postgres server
  2. Let your computer sleep for a while, possibly overnight
  3. Wake up and try to do any operation on the context menu of the table
  4. See error

Expected behavior
If the connection is timed out or lost, it should automatically reconnect and be able to resume operation

Screenshots
image

Desktop (please complete the following information):

  • OS: Mac

ADS (please complete the following information):

  • ADS Version

Version: 1.45.0
Commit: 8eff468100f02157f2219335f7a566d14451ca49
Date: 2023-07-24T18:20:58.743Z (1 wk ago)
VS Code: 1.79.0
Electron: 22.3.14
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Darwin x64 22.3.0

  • ADS PostgresSQL etension version
    V.0.5.0

Additional context
Earlier before updating to current version session id error used to appear as described in #423

@nasc17 possibly a related error occurs when trying to expanding node
Failed to expand node: consuming input failed: Operation timed out
SSL SYSCALL error: Operation timed out

image
nasc17 commented

@nasc17 possibly a related error occurs when trying to expanding node Failed to expand node: consuming input failed: Operation timed out SSL SYSCALL error: Operation timed out

image

Are you still using the v0.5.0 extension seeing this error or insiders?

I have v0.5.0 installed
image

@nasc17 another one similar is when trying to run a query on query editor

None
Error while rolling back open transaction due to previous failure: None

image
nasc17 commented

Thank you for the added information. We are working on getting out a release to address the issue. Will keep you updated on how to verify fixes shortly.

nasc17 commented

Bug has been addressed in our unstable release of PostgreSQL extension v0.5.1-insiders. We would appreciate your verification that it has been handled appropriately.