2026/04/20
Jump to navigation
Jump to search
|
Monday, April 20, 2026 (#110)
|
|
References |
transcribed retroactively from a Signal chat
- 12:30 Today's fun code-problem is that the Updater is somehow trying to access a Buffer that has been closed, presumably meaning that it's the wrong Buffer (Gromit) and something isn't getting set or reset properly.
- 14:44 Looks like something is creating a new Session (process) object instead of using the existing one (which is also necessary for other reasons, i.e. maintaining the executable's internal state).
- 14:55 ...caused, apparently, by a redundant call that was the only way I could think of to get a thing started when it is a file (full of commands) instead of a string.
- Okay. So I need a correct way to handle that.
- 15:53 NTS: the Command-object has to be what creates the Session, because what the command executes is what starts the session (in proc, anyway, and therefore necessarily in the class-model).
- 20:53 Currently (as of the last 20 minutes or so) dealing with a situation where the data starts getting written to the output stream, and then mysteriously stops. It makes my head get all slushy when I try to puzzle it out, but that's pretty much de rigeur (or perhaps de rigour mortis) these days 😵💫.
- 20:55 Oh, duhh -- is because the output stream got backed up, so zero bytes got written, but code misinterpreted that as an error. Ok. Onward...
- 20:55 Something is working right, because it's actually creating some tables now!
- 20:56 ...an' they gots data innem!
- Still erroring out at some point, tho.
- 20:57 Timeout issue. ...and the screen updater seems to have gotten disconnected again. >.<
- 20:59 Actually, no, updater is working -- it's just stopping because output is hanging. I bet I know what's happening: there's an error, which is closing the output stream, but it's not getting caught -- so code keeps trying to send to a dead stream.
- 21:03 Huh, no! It's getting stuck after writing successfully.
- 21:31 It's timing out even though stuff is being written to the screen...
- ...but also, the Updater isn't being called from inside the loop, so I'm just getting debugging output...
- 21:48 The problem is that the Updater can't be accessed from there... or, at least, I don't think it can; guess I should double-check that.
- 22:14 Actually, it's a class global, so yeah... and now the problem is that the Updater's Panel isn't getting initialized properly, and sorting that out means sorting out where it's declared and how it's accessed, which is looking like a Tomorrow Thing.