VS Code DBT Extension Registration Message Won't Go Away

Help
1

Often times when I restart my computer and launch VS Code to use dbt I get a warning message that says “You must register and verify your email address to continue using the dbt extension.” When this happens I click the Register Now button which launches a browser and takes me to dbt.com. After I log in, it asks me to select an account from one named after my company and one called Snowflake Partner Connect. It doesn’t seem to matter which of these I select. After doing so I get a message that says “Success! Your dbt extension is now active.”

Is there a way to make this message go away permanently so I don’t have reregister every day!

image
image757×607 32.8 KB

Put code inside backticks
  to preserve indentation
    which is especially important 
      for Python and YAML!
2

Oof. I have the same issue. Not sure if this is the same for you, but I am connecting to a project in WSL on my machine.

Note: @Justin Grimes originally posted this reply in Slack. It might not have transferred perfectly.

3

WSL? World Surf League?

4

Windows Subsystem for Linux

Note: @Justin Grimes originally posted this reply in Slack. It might not have transferred perfectly.

5

Nope. We’re on Windows 11.

6

Can you share your extension version? Our eng team is investigating. Thank you!

Note: @Connie Carey originally posted this reply in Slack. It might not have transferred perfectly.

7

I am on v0.34.1

Note: @Justin Grimes originally posted this reply in Slack. It might not have transferred perfectly.

8

Hi (I’m on the eng team), could you share the extension logs please?

You should find them in `c:

Note: @dakota originally posted this reply in Slack. It might not have transferred perfectly.

9

Hi (I’m on the eng team), could you share the extension logs please?

You should find them in c:\users\<username>\AppData\Roaming\Code\User\globalStorage\dbtlabsinc.dbt\logs

You can also click on the dbt Extension status bar item, which will bring up a console message that should contain the LSP executable path. The logs are a sibling of the bin directory.

Note: @dakota originally posted this reply in Slack. It might not have transferred perfectly.

10

2 things.

  1. I am connecting to a repo in a remote workspace (WSL) on my computer and I dont see that directory on the windows side. Maybe it is somewhere on the WSL side?
  2. It usually says that I dont have an lsp running, but this is going on forever:

Note: @Justin Grimes originally posted this reply in Slack. It might not have transferred perfectly.

11

today it gives me the option to clear my cache but it just spins as well:

Note: @Justin Grimes originally posted this reply in Slack. It might not have transferred perfectly.

12

I don’t think we’ve ever tested using a remote workspace using WSL. I wonder if VSCode runs the extension in the within WSL. I’ll need to test that out and get back to you!

If you’re using something other than VSCode (Like Cursor), the logs might also not be in the “Code” folder, but something like “Cursor”

Note: @dakota originally posted this reply in Slack. It might not have transferred perfectly.

13

Dakota, I can’t post the logs online because it might not be okay with my company. Is there a different way we can communicate about this? My company pays for dbt licenses. Thanks!

1 Like
14

hey @Arthur , the best way troubleshoot this and send your logs would be to email our mighty support team. Could you please email support@getdbt.com and reference this conversation you’ve had with our Engineer (Walter) ? Many thanks!

15

We’ve identified the root cause of the issue, and will be shipping a fix soon. Can’t put any specific timeline on it, but we are prioritising the fix.

Note: @dakota originally posted this reply in Slack. It might not have transferred perfectly.

1 Like
16

Thank you, Mirna and Dakota! :slight_smile:

17

Hey all, this should be resolved. Please let us know if the fix worked for your setup!

The root cause is that our refresh tokens only had a lifespan of 8 hours, so if you quit VSC at the end of your work day the refresh token expires before you log on again. We have bumped the lifespan to 7 days which should reduce the frequency of these login requests if you develop in VSC frequently.

Note: @Connie Carey originally posted this reply in Slack. It might not have transferred perfectly.

18

That refresh token being expanded did the trick. thank you for the quick turnaround!

Note: @Justin Grimes originally posted this reply in Slack. It might not have transferred perfectly.

19

This might be just a me thing, but you might want to change the wording around it to make it more apparent to user that it isn’t so much a “sign up” type process as a sign-in required/token refresh required kind of operation.

Note: @Justin Grimes originally posted this reply in Slack. It might not have transferred perfectly.

20

:smile: we are literally working on that right now! :spiderman_point: it’ll say “Your dbt extension session expired. Sign in again to continue using the extension.”

Note: @Connie Carey originally posted this reply in Slack. It might not have transferred perfectly.