It seems likely that the HTML generated from the Markdown is longer than 30,000 characters, even though the Markdown you've entered is shorter. There's an existing issue for this. Ideally when this is fixed the limit will apply only to the Markdown, as you would expect.

I don't know of a workaround other than finding a way to remove enough characters to bring the HTML under 30,000 characters. Without knowing how long the HTML is, this could require losing anything from 1 character to a few thousand (my example linked from the issue hit this problem somewhere above 27,000 characters, but that might have been an extreme example with a lot of Markdown elements that dramatically increase in size.

You might be able to estimate how many characters the HTML takes by viewing it in the developer window and then pasting it into a character counter (such as a new post). I'd save your draft post in a text file first just in case.

Obviously you shouldn't have to do this, so I'm just mentioning it as the best workaround I can think of until this is fixed.

Thanks to trichoplax‭'s fast work we have a fix for this in process (with possibly a better fix later). Save your post draft if you haven't already; you should be able to post it soon.

Thanks for looking into this. Please let me know when a fix has been deployed.

We've just pushed a fix for this. The short form is that a smaller amount of markdown can lead to a much larger amount of HTML, and we were not properly accounting for that.

Monica Cellio‭ Thanks for letting me know but unfortunately I still can’t post my review request despite my markdown being less than 30,000 characters. I have updated my post to show the new slightly different error message. It now states my body markdown is too long.

I could try to email my markdown to someone in Codidact if that would be helpful.

That's another issue (just discovered yesterday as part of testing the fix for this issue).

I was hoping it wouldn't restrict you, since it doesn't reduce the character limit as much as the previous bug, but it seems you're close enough to the limit to still be affected.

Note that the mention of Windows line endings doesn't make it a Windows specific problem - it affects anyone on any operating system. It effectively loses you 1 character of limit for each new line in your post. For example, if you have 1,000 lines in your post, you will go over the limit at 29,000 instead of 30,000. This should give you an idea of how close you are to the limit to help you decide if it's worth trying to reduce lines or characters as a workaround.

Again, you shouldn't have to do this - it's just a potential workaround while we work out how to fix this.

Ouch, I'm sorry! Thanks for offering the markdown; you can send it to [email protected] and I'll work with our developers to figure out what's going on.

My proposed review request post has less than 30,000 characters of markdown but with the new line issue the total number of characters is about 30,400. When the new line issue is resolved, hopefully I can post my review request.

We've pushed another fix and specifically tested it with your post. Before I status-tag this again, would you care to make the post to confirm in prod? Thanks.

Monica Cellio‭ I successfully posted my code review request and shortly thereafter I successfully made a tiny edit to my post. So everything seems fine to me. Hurrah!

Please pass on my thanks to everyone who helped resolve this problem.

Thanks for your patience! We learned things from investigating this bug, if that's any consolation. :-)

Trichoplax: You made some suggested edits to my successfully posted code review request. Unfortunately when I went to examine your suggested edits in the before and after view, it showed my entire post and not just the neighborhood of your proposed changes. Additionally, both the before and after views were bolded for my entire post.

As a result, your proposed changes were hard to see.

I humbly request that you make no more suggested edits for my code review request post.

will.octagon.gibson‭ I apologise for the unhelpful suggested edits. I've raised the problem of the entire post being highlighted in the diff as https://github.com/codidact/qpixel/issues/2122 and we're working to fix it. I won't be making any suggested edits until that is resolved.