Thomas Leonard

I think you can just `git pull` my branch into yours to fix it.

Or I can open a PR against this branch if you prefer. The logs for the fuzz failure on your branch look like this: ``` +dispatch_commands: done +client-to-server: receiver ready...

OK: https://github.com/hannesm/ocaml-tls/pull/5

Ah, I think we need a slight update to the CI too. If a package can't be tested on *any* platform then it fails the analysis stage. Since ocaml-ci doesn't...

Closing as the original issue is now fixed. I've opened a separate issue for back-pressure: #760

> We want the job scheduling algorithm to take cache hints into account, but also to consider worker capacity and availability. It should already be doing that: https://github.com/ocurrent/ocluster/blob/a27ef61876471fa5620d2422fef441bf50d0260f/scheduler/pool.ml#L368-L373 However, there...

I haven't look at the individual issues, but I would guess such problems mosly occur when you send malformed data, which Eio shouldn't be doing. So Eio using uring shouldn't...

> We could drop Eio-uring down to a non-default mode that's activated by an environment variable, @talex5? Just set `EIO_BACKEND=posix`. Or we could just get rid of fixed buffers.

It also affects eio_posix (I've updated the title).

You can count how many steps have failed with https://github.com/ocurrent/ocurrent/blob/e43b6c5c896a4cc5ca5c1d0cfbf10a6401fbcd47/lib_term/s.ml#L54-L62 You can also write your own driver. e.g. OCurrent's own tests use this: https://github.com/ocurrent/ocurrent/blob/e43b6c5c896a4cc5ca5c1d0cfbf10a6401fbcd47/test/driver.mli#L10-L12