Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OK button is disabled #23473

Closed
ranjCS opened this issue Jun 26, 2023 · 16 comments
Closed

OK button is disabled #23473

ranjCS opened this issue Jun 26, 2023 · 16 comments

Comments

@ranjCS
Copy link

ranjCS commented Jun 26, 2023

  • Azure Data Studio Version:
    1.44.1
  • OS Version:
    Windows 11 Enterprise
    Steps to Reproduce:
  1. Select the source DB,
  2. Select the target DB
    I expect the OK button button to be enabled so I can click, but it is not. Any reason for that?

Does this issue occur when all extensions are disabled?: Yes/No
No

image

@kisantia
Copy link
Contributor

@ranjCS does this consistently happen? If you close and reopen the dialog does this still happen?

@ranjCS
Copy link
Author

ranjCS commented Jun 27, 2023 via email

@kisantia
Copy link
Contributor

@SakshiS-harma can you please look into this? Sounds like it might be a race condition

@SakshiS-harma
Copy link
Contributor

@ranjCS can you provide the application logs when this issue happens?

  1. Is there a particular server/database with which this issue happens or it happens consistently for all/any server/db combination?
  2. Is/Are the server/s connected before starting Schema compare or are they added from the blue "Connect" icon from this dialog?
  3. Is/Are the server/s really connected?
  4. Has this issue happened before or are you seeing it after an update as a regression?

@ranjCS
Copy link
Author

ranjCS commented Jun 30, 2023 via email

@SakshiS-harma
Copy link
Contributor

Hi @ranjCS, just to clarify this issue only happens when editing/choosing a new connection in the schema compare dialog? Is it while updating server or database that this issue happens?
From what I am reading, it sounds like if the servers are already connected and selected along with populated dbs dropdown- the issue doesn't happen. It only happens when the db is changed?

Also, in the last reply, no images were posted, can you share the email on sakshis@microsoft.com

@ranjCS
Copy link
Author

ranjCS commented Jul 7, 2023 via email

@SakshiS-harma
Copy link
Contributor

Do you mind sending this email to sakshis@microsoft.com . The images attached here aren't visible.

Thanks for confirming that the issue happens when database is updated. It is a helpful piece of information for further investigation.

@SakshiS-harma
Copy link
Contributor

Hi @ranjCS , just wanted to check, is it ok if I share a private built vsix with you for collecting some logs ? I have some additional logging turned on to figure out what the issue is. I haven't been able to repro the issue at my end and I am not sure why this might be happening. Let me know if it works, and I will share the schema compare vsix with you.

@ranjCS
Copy link
Author

ranjCS commented Jul 20, 2023 via email

@SakshiS-harma
Copy link
Contributor

The logs are devoid of any server/database-specific information, making them safe for sharing.

@SakshiS-harma
Copy link
Contributor

SakshiS-harma commented Jul 28, 2023

Hi @ranjCS , I sent out an email to you with a custom VSIX for further investigation. Hope to hear back from you on this.

@github-actions
Copy link

We need more info to debug your particular issue. If you could attach your logs to the issue (ensure no private data is in them), it would help us fix the issue much faster.

  1. First open the Settings page, find the Mssql: Tracing Level setting and change that to All then restart Azure Data Studio.
  2. Open command palette (Click View -> Command Palette) and run the command Developer: Set Log Level... and set the level to Trace.
  3. Run the repro scenarios.
  4. Collect the following logs:

Console Logs

  • Open Developer Tools (Help -> Toggle Developer Tools)
  • Click the Console tab
  • Click in the log area and select all text (CTRL+A)
  • Save this text into a file named console.log and attach it to this issue.
  • Developer Tools can be closed via Help -> Toggle Developer Tools

Application Logs

  • Open command palette (Click View -> Command Palette)
  • Run the command: Developer: Open Logs Folder
  • This will open the log folder locally. Please zip up this folder and attach it to the issue.
  1. Now you can revert the Log/Tracing levels changes made in step 1 and step 2.

@SakshiS-harma
Copy link
Contributor

@ranjCS Just checking if you have any update/logs for me to dig deeper into the issue.

@SakshiS-harma
Copy link
Contributor

@ranjCS Gentle reminder that I need some more logs to continue working on this issue. If not, then unfortunately I will have to close this issue and you can open it once you have some logs for me to work on.

Thanks! Hoping to hear back from you.

@SakshiS-harma
Copy link
Contributor

@ranjCS I am closing this issue for now, since I haven't received any response from your end and I have no further data to work on this issue. Please re-open it if you have any new logs for me to work with.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants