Long responses result in what looks like zalgo text

[nupchurchTCN]

Very large responses seem to collapse into a single line:

The UI also lags after attempting to interact with this line of text.

[danirod]

Creepy. What operating system or DE is this? I am a typography freak and I am trying to guess from the screenshot, but I am 50% KDE, 50% Windows.

I have tried to replicate this by defining an endpoint that returns two copies of the Quixote (2.1 MB) and cannot seem to trigger the bug.

The endpoint URL is https://gist.githubusercontent.com/danirod/3ab949633487bde1512fc20ceed9551c/raw/3228529cc73757dbec196b32a4d4ce1be262581c/gistfile1.txt, in case you want to give it a try.

[nupchurchTCN]

I can't trigger the bug with that endpoint either; maybe the response has to be JSON?

What operating system or DE is this?

My org-provided laptop (unfortunately) runs Windows 11. I might try to replicate the bug on my EndeavourOS machine to see if this is a Windows thing.

[danirod]

Aha, managed to replicate this!

My demo is mistaken because it has to be a very long line, not a very long response. For instance, this one breaks indeed Cartero: https://gist.githubusercontent.com/danirod/6afc67718870d6dab163da220d16b0dd/raw/968f86c2cd8212b80a30660b0106bfb9007251dc/gistfile1.txt

It is the same text, as the first one, but in a single line. Mind, we are talking about roughly 2 million characters in a single line as this is a 2.1 MB file. Everything is slow too.

When the mode is set to wrap lines, the first lines are rendered OK, but eventually it collapses.

I made some research, the bug is related to pango and it seems to happen everywhere, as the screenshots in the upstream issue are made on Fedora.

I think the best I can do for now considering that the issue has a few years and has been moved from repo to repo, is to detect if a line has more than 10.000 characters and if that's the case show a warning similar to the one presented when the file is binary. Something like "hey, this response has very very very very very long lines and the editor may collapse, want to export the response as a file instead?"

Not being fixed for 25.1 because we are already in string freeze, but it will probably make a cut for 26.0.

[nupchurchTCN]

Ah, this makes sense as the response I'm getting likely contains long user bios (not entirely sure as I can't read the response lol). It's a shame to see such an issue go unresolved for so long upstream.

Your solution sounds pretty ideal under the circumstances; thanks for looking into this!