Logs full of stacktraces for "normal" errors?

No, not at all :slight_smile: A clean log is a good log. Ideally, the only instances of “ERROR” would be when there’s actually an error for you to pay attention to. It’s a challenge for us to maintain this state, but it’s worth striving for.

Please feel free to open edx-platform issues for any spurious error or warning you notice @antonofthewoods. I can’t guarantee we’ll get to all of them, but it will be good to have them recorded anyway. You can add the help wanted label to encourage volunteer contributors to pick up the issues, and of course you are welcome to tackle any of them yourself. Feel free to tag me on GitHub if you need pointers / sanity checks.

(Trivia: My proud “Warning Squasher” badge is just a participation award from the last time we made a concerted effort to clean up the logs.)

2 Likes