💾 Archived View for bbs.geminispace.org › u › mbays › 3726 captured on 2024-05-26 at 17:25:20. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2024-05-10)

➡️ Next capture (2024-06-16)

🚧 View Differences

-=-=-=-=-=-=-

Comment by 🚀 mbays

Re: "Streaming bugs and UX improvements"

In: s/Lagrange-Issues

Now I have seen the same truncation bug on Android (not with the test script linked above, but with something else similar which prints more on each line). The client becomes entirely unresponsive and needs to be restarted. (This may have been a fairly old version of lagrange for android, but the same bug is still observed on linux desktop with yesterday's latest git.)

🚀 mbays [OP]

2023-07-31 · 10 months ago

1 Later Comment

🕹️ skyjake [mod...] · 2023-08-11 at 15:28:

v1.16.7 has a workaround for Bug 1 and resolves Bug 2.

Testing with Gemski, sometimes the updated content has a partial line, with incomplete ANSI sequences of course. I should still improve this to ensure that during streaming updates only complete lines are included in the page.

Original Post

🌒 s/Lagrange-Issues

Two or three bugs with streamed gemtext in Lagrange (latest dev branch). Bug 1: truncation Occasionally, the streamed page is truncated in the output, even though the connection to server stays alive. It seems to always show complete lines, but sometimes all lines after some point are not shown, even if the stream is appended to. Test case: [gemini link] This is running the following cgi shell script: [preformatted] Running this locally, I find Lagrange truncates the page after some random...

💬 mbays · 5 comments · 2023-06-11 · 1 year ago · #bug #feature