Improve error message when dbt or warehouse credentials are missing
See original GitHub issueDescription
Error message for missing credentials doesn’t make sense and is hard to track back to the original error. in this case the personal access token was missing but the message said “could not read Password…”
Compiling
Error 00:00:01
UnexpectedServerError: Error: Cloning into '/tmp/git_fa8eb50cbaf2d97a4cb80bdffeefa998'... fatal: could not read Password for 'https://*****@github.com': terminal prompts disabled
App Version
v.187.0
Issue Analytics
- State:
- Created a year ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Debugging errors - dbt Developer Hub
To fix this: Open the offending file (e.g. schema.yml ); Check the line in the error message (e.g. line 5 ); Find the...
Read more >dbt compile should not need service account credentials #2239
When running dbt compile I get an error stating that GOOGLE_APPLIATION_CREDENTIALS is missing. compile builds run read models and sql ...
Read more >while running the dbt run command gets error - Stack Overflow
Check the profile key in your dbt_project.yml · Check the profiles you have in your profiles.yml · Run dbt debug --config-dir to check...
Read more >dbt Guide - GitLab
This should be done carefully; using a larger warehouse increases performance but will greatly increase cost! Err on the side of using smaller...
Read more >DBT-00001 to DBT-50002 - Oracle Help Center
Database Error Messages ... DBT-00201: Invalid database credentials wallet location string. ... Action: Upgrade the existing ASM instance to version %s.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Understood! I’ll open a new issue that should improve the error message here to make it more obvious where the error is coming from and link to this issue
Is this issue still relevant? There have been no updates for 60 days, please close the issue or keep the conversation going!