-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat: extend logging in db.py and dbview.py #852
Conversation
@puehringer Is there a way to enable debug logging without passing the whole logging config? Setting
|
We maybe should pin pyright, as it often comes to these patch version which break the build: https://github.com/datavisyn/tdp_core/blob/develop/requirements_dev.txt#L2
because the However, we could think about adding a second setting (like log_level, default None), and if it is set we "inject"/merge it into the logging setting? Or we add a second setting which is deep-merged. How does that sound? |
Thanks for the hint for the pyright dependency. Yes, good idea. The most common change is probably the debug level. So let's add an option to it and merge/override it into the default logging config if set. I'll file a PR in visyn_core. |
Here you go: datavisyn/visyn_core#69 |
## What's Changed ### Features * Extend logging in db.py and dbview.py by @thinkh in #852 ### Bugfixes * Migrate local to remote graph without intermediate requests by @thinkh in #850 **Full Changelog**: v20.0.1...v20.1.0
Developer Checklist (Definition of Done)
Issue
UI/UX/Vis
Code
PR
release: minor
) to this PR following semverCloses #...
)Summary of changes
Enable the debug logs via env variable
VISYN_CORE__LOG_LEVEL=DEBUG
or invisyn_core.log_level
the config.json:Screenshots
Example:
Additional notes for the reviewer(s)
@puehringer I added my logs with the log level DEBUG. Is it ok like this or should I add a separate flag to the tdp_core settings to enable the very specific case of logging db.py and dbview.py?
Thanks for creating this pull request 🤗