Jennifer Richards

Another case seen recently: a submission failed with an error message `Error: Expected version="3", but found "0"`. I'm not sure whether this really had a `version="0"` or if there simply...

Yet another: a draft came in with ``. This resulted in no actual error message in the log, just a useless "see above" message. Running it through xml2rfc revealed errors...

A file failed submission because of`version=""` in the`` element. This is accepted without comment by xml2rfc, but causes the following error in the celery logs: ``` [2023-08-22 07:09:25,002: WARNING/ForkPoolWorker-2] ietf/submit/utils.py(1328)...

As noted on #6221, that PR improves the status page to be less confusing after an error occurred but we should do a better job actually handling the errors we've...

> It would be good to be more transparent about what the failures actually _were_. Yes. There's some existing code that grabs exception messages and logs them in the event...

#6158 related item that should be reflected clearly on the submission status page. I've renamed this ticket to be more specific about what it's evolved to track.

#7107 is another case that should be addressed

Another case is in #7405 (a `` element using the `src` element instead of using inline content)

Also seeing this when using a custom through model when it has its own `HistoricalRecords`. ```python class Label(models.Model): # ... history = HistoricalRecords() class ThingLabel(models.Model): thing = models.ForeignKey("Thing", on_delete=models.CASCADE) label...

It's still an issue as much as it ever was, but I think a "fix" will be far more complicated than appropriate. Closing as "don't care."