-
Notifications
You must be signed in to change notification settings - Fork 185
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
RESTClient: docs: add the troubleshooting section #1367
Conversation
✅ Deploy Preview for dlt-hub-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
||
```bash | ||
RUNTIME__LOG_LEVEL=INFO python my_script.py |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is INFO
level sufficient here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this is enough to see the requests info
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀 imo we need to improve exceptions and logging as @rudolfix already did maybe we can do extended logging and rich formatted exception logs if level=DEBUG
?
Good point @sultaniman. Do you have good examples of rich formatting the exceptions? I think one thing that would be great is to see the actual response content in case of HTTP exceptions, as sometimes there's required context that can clarify the error. |
@burnash I only know about rich traceback printer https://rich.readthedocs.io/en/stable/traceback.html |
No description provided.