=> Re: "Streaming bugs and UX improvements" | In: s/Lagrange-Issues
@skyjake Hmm, I guess also if there's a lengthy pause due to network delays the user could want to know when new data comes in.
2023-06-11 ยท 2 years ago
=> ๐ mbays [OP] ยท 2023-06-18 at 07:32:
This infstreamtest test seems to work fine on Android (I don't know what Lagrange version, but could find out). It remain broken with latest dev on my linux machine.
=> ๐ mbays [OP] ยท 2023-07-31 at 22:40:
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.)
=> ๐น๏ธ 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.
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 ยท 2 years ago ยท #bug #feature This content has been proxied by September (ba2dc).Proxy Information
text/gemini; charset=utf-8