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
[Bug] Bad argument sent to logging in tracking function #9753
Open
2 tasks done
Labels
bug
Something isn't working
Medium Severity
bug with minor impact that does not have resolution timeframe requirement
Comments
5 tasks
Thanks for opening an issue and PR (#9754) for this @pol-defont-reaulx ! What are the consequence(s) and/or impact of |
The consequence is a bad labelling of the request's type when pushing logs to Snowplow for POST requests. It's not a critical bug at all of course. |
Makes sense! |
dbeatty10
added
Medium Severity
bug with minor impact that does not have resolution timeframe requirement
and removed
triage
labels
Mar 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
Medium Severity
bug with minor impact that does not have resolution timeframe requirement
Is this a new bug in dbt-core?
Current Behavior
In core/dbt/tracking.py, the string argument sent to _log_result for http_post is not the right one. It's "GET".
Expected Behavior
The argument sent should be "POST"
Steps To Reproduce
In the code
Relevant log output
No response
Environment
No response
Which database adapter are you using with dbt?
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: