| 10 Jun 2026 |
 zoë (@blokyk) | 
Download image.png | 08:43:02 |
| zoë (@blokyk) | (i will say that it's happened a lot less and the improvements from this release are great anyway) | 08:43:40 |
 maralorn | That's lix? Does the nom process keep running for a while without this going away? | 09:05:48 |
| zoë (@blokyk) | yep, lix 2.95.3 (though the builder uses cppnix 2.34.4, if that's relevant) | 09:06:38 |
| maralorn | That's a FOD, right? I wonder if they behave differently... | 09:06:42 |
| zoë (@blokyk) | once the build is finished nom exits normally | 09:07:00 |
| maralorn | No, I mean had nom already exited when you took that screenshot and how long did nom run after the build had finished? | 09:10:17 |
| maralorn | But I guess at least 4 seconds. | 09:10:35 |
| maralorn | At this point I wonder whether this is a bug in the lix daemon. | 09:10:58 |
| zoë (@blokyk) | no nom was still running when i took the screenshot, and it kept displaying those as unfinished until the whole build finished | 09:12:01 |
| maralorn | Wild | 09:12:54 |
 Primrose (== Léana) | That happened yesterday to me at midnight and I wasn't sure if it was a non-functional overlay on my side, so I didn't report it | 10:10:21 |
| Primrose (== Léana) | 
Download nom-is-still-broken.png | 10:11:06 |
| Primrose (== Léana) | I think I had lix 2.95 | 10:11:16 |
| Primrose (== Léana) | * I think I had lix 2.95 when it happened | 10:11:24 |
 K900 | I'm getting something funny | 10:11:33 |
| K900 | A lot of "runHandler: couldn't find handler" | 10:11:36 |
| K900 | After a build ends | 10:11:39 |
| K900 | I think those are coming from nom? | 10:11:46 |
| maralorn | So essentially the problem isn’t solved? | 10:33:45 |
| maralorn | Maybe have a screenshot? That sounds very weird. Maybe something to do with the inotify lib. | 10:34:23 |
 ryndubei | looks like a bug with hinotify in fact, it has this in the source:
runHandler (wd, event) = do
handlers <- readMVar em
let handlerM = Map.lookup wd handlers
case handlerM of
Nothing -> putStrLn "runHandler: couldn't find handler" -- impossible?
Just handler -> handler event
| 10:47:26 |
 alexfmpe | The 'impossible' has happened | 10:48:24 |
| Primrose (== Léana) | It was, and then it wasn't | 11:01:41 |
| Primrose (== Léana) | I am not sure what changed during | 11:02:04 |
| maralorn | Maybe a difference between fsnotify and hinotify? | 11:03:13 |
| maralorn | Oh, boy. Don’t tell me we have to bisect this. | 11:03:23 |
| maralorn | I believe what this means is simply that nom has exited the withWatch scope before all watches have been destroyed. Kinda something which something a borrow checker would prevent.^^ | 11:18:54 |
| maralorn | * I believe what this means is simply that nom has exited the withWatch scope before all watches have been destroyed. Kinda something which something like a borrow checker would prevent.^^ | 11:19:00 |
| maralorn | Oh, boy. This sucks. I even had nearly a complete and detailed lix issue written yesterday and then my computer shut down and I lost my input field. 🤦 | 11:20:02 |
