Closed mjsir911 closed 5 months ago
Hey @mjsir911 I have read and I can say that I approve this contribution to djangosaml2 that improve the debug information when some error might be critical for a production system
I look forward for the resolution of the issues we have in the unit tests, you can see how the CI fails. When these issues will be fixed I'll ask you to increase the version of djangosaml2, then we'll be able to merge and tag a new release
@peppelinux fixed the tests
ok, let's then do this release
can you please set 1.9.1 here? https://github.com/IdentityPython/djangosaml2/blob/master/setup.py#L30
done @peppelinux
Hi,
We were running into an old issue #294 that got resolved back in 1.3.1 #297, but it took us a bit to track down because we were getting them through email and weren't seeing any traceback info.
This PR enables traceback info to any logging calls that are might include traceback info / are inside exceptions.
Additionally it might be possible to remove the
f"{e}"
from these logging calls since it's now included in the traceback / exception info that shows up in the logs, but I haven't done that since y'all do that elsewhere too.