#Using structlog in debug mode triggers an exception

1 messages · Page 1 of 1 (latest)

potent flower
#

Hello, it seems that I'm running into the same issue as the one reported here, even though it has been closed:
https://github.com/litestar-org/litestar/issues/1672

I'm using the latest version of Litestar and structlog, and reproduced this behavior using the MVCE from https://github.com/litestar-org/litestar/issues/1804

Should I comment on the original issue or create a new one...?

GitHub

Description Using the default StructLoggingConfig for logging causes the application to fail to start with litestar run --debug. URL to code causing the issue No response MCVE from litestar import ...

GitHub

Description The error issue from #1672 was resolved in #1742; however, the log levels should properly be set when --debug is set with the CLI. URL to code causing the issue litestar/litestar/app.py...

ruby isle
#

@potent flower litestar#1804 is open for this, iirc.

It is something I need to get back to