Open timmc-edx opened 2 months ago
I suspect this is actually a bug in the code that creates the event data in the first place. For example, that course_key=None
is very suspicious; a spot-check of successfully sent messages on that topic shows a non-None course key, and the code that sends the event does not indicate that the course key is optional.
We have intermittently seen errors involving "None cannot be handled by custom serializers" when producing to the event bus.
Example log message that has been pulled apart for readability, and redacted:
Another event on a different topic and with a different signal:
The traceback is the same: