-
-
Notifications
You must be signed in to change notification settings - Fork 399
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
fix: logging to file with structlog #3425
Conversation
537ab26
to
5316be2
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3425 +/- ##
=======================================
Coverage 98.27% 98.27%
=======================================
Files 328 328
Lines 14851 14852 +1
Branches 2357 2357
=======================================
+ Hits 14595 14596 +1
Misses 117 117
Partials 139 139 ☔ View full report in Codecov by Sentry. |
5cbefa1
to
a1d783e
Compare
a1d783e
to
d8d8b55
Compare
Fixes issue where adding a file handle to the config object would cause it to fail on call to `configure()`. - add e2e test for logging to file w/ structlog
d8d8b55
to
0c920f0
Compare
Quality Gate passedIssues Measures |
Documentation preview will be available shortly at https://litestar-org.github.io/litestar-docs-preview/3425 |
fix: structlog file logging Fixes issue where adding a file handle to the config object would cause it to fail on call to `configure()`. - add e2e test for logging to file w/ structlog (cherry picked from commit cc6d55b)
fix: structlog file logging Fixes issue where adding a file handle to the config object would cause it to fail on call to `configure()`. - add e2e test for logging to file w/ structlog (cherry picked from commit cc6d55b)
Description
PR fixes issue with converting
StructLoggingConfig
to dict during call toconfigure()
when the config object has a custom logger factory that references aTextIO
object, which cannot be pickled.Closes