microsoft / azuredatastudio-postgresql

azuredatastudio-postgresql is an extension for Azure Data Studio that enables you to work with PostgreSQL databases
Other
193 stars 36 forks source link

Object Explorer shows empty objects and behaves strangely #456

Open yorkshirelandscape opened 11 months ago

yorkshirelandscape commented 11 months ago

Describe the bug When connected to my postgresql db, the object explorer show the expected folders, but when I expand any of them, the objects within are all empty, showing only the arrows on the left. If I mouseover, I'll see the icons, but no names. Sometimes, the other folders will have disappeared.

I can try to open queries in these empty-looking databases, but they all seem to be the postgres database and clicking the database dropdown in the query editor shows no other databases.

The Manage view doesn't show anything. It just spins or is empty.

I figured this was a permissions problem somehow, but I'm able to browse all these objects with no problem in DBeaver.

To Reproduce Steps to reproduce the behavior:

  1. Create pgsql superuser with encrypted password access and all privileges on all databases.
  2. In ADS, create connection to pgsql server with created user. No special settings. Just password authentication.
  3. Open object explorer and click into any folder.

Expected behavior I expect to see the objects (databases, roles, etc.) appear normally with names and icons and for the other folders to shift downward.

Screenshots

image image

Desktop (please complete the following information):

ADS (please complete the following information):

Additional context PostgreSQL is running on a Debian 12 container on my Proxmox server

DaeunYim commented 11 months ago

Hi @yorkshirelandscape is your Mac using an intel CPU or Apple silicon?

Also, could you please provide any error logs you can find in these directories: /Users//Library/Application Support/sqlops/pgsql /Users//Library/Application Support/azuredatastudio/logs (esp. /Users//Library/Application Support/azuredatastudio/logs//exthost1)

We weren't able to reproduce this issue on both Intel CPU and Apple Silicon, so more detailed information would be helpful.

yorkshirelandscape commented 11 months ago

Hi Daeun. It's an Apple silicon. M1 MacBook Pro.

Here are the logs: logs.zip

nasc17 commented 7 months ago

Hi Daeun. It's an Apple silicon. M1 MacBook Pro.

Here are the logs: logs.zip

Hi @yorkshirelandscape we have an update to the extension. Please try the latest stable release of PostgreSQL extension v0.6.0 and Azure Data Studio v1.47.0. Let us know if issue still persists

yorkshirelandscape commented 7 months ago

Hi @yorkshirelandscape we have an update to the extension. Please try the latest stable release of PostgreSQL extension v0.6.0 and Azure Data Studio v1.47.0. Let us know if issue still persists

No luck, I'm afraid. Same behavior.

nasc17 commented 7 months ago

@yorkshirelandscape thank you for checking. Please follow these steps just to confirm the changes from our new binaries are in and then provide us with updated logs:

Navigate to "/Users//.azuredatastudio/extensions" and delete any existing PostgreSQL extensions. Don't worry about losing your connection information, as they will reappear once you reinstall the extension.

Once you have completed these steps, please try downloading and installing the new version of the PostgreSQL extension again.

Attempt again expanding the folders again, then provide any error logs you can find in these directories: /Users//Library/Application Support/sqlops/pgsql /Users//Library/Application Support/azuredatastudio/logs (esp. /Users//Library/Application Support/azuredatastudio/logs//exthost1)

yorkshirelandscape commented 6 months ago

Sorry it's taken me so long to get back to you. At the risk of overdoing it, here are all the logs for a brief session in which I experienced the error after manually deleting the extension and reinstalling it. 20231219T052439.zip ossdbtoolsservice.log

nasc17 commented 6 months ago

@yorkshirelandscape thank you for the logs. We will inform you when this has been addressed in the insiders release in order for you to test against.