Sonja Heinze

Hi @barracuda156 and @ceastlund, given the problems that currently make it very difficult to have `ppx_bisect` actively maintained, there are already people who have added `ppxlib.0.28.0` support on their own...

Hi @aantron, a kind reminder and update on this: This PR makes `bisect_ppx` compatible with the latest compilers. It's also the first step to making it compatible with the latest...

> @pitag-ha, as the ppxlib maintainer, could you comment on the correctness of patches like https://github.com/anmonteiro/bisect_ppx/commit/cc442a08e3a2e0e18deb48f3a696076ac0986728 for 0.28.0? Thanks for reaching out on that! https://github.com/anmonteiro/bisect_ppx/commit/cc442a08e3a2e0e18deb48f3a696076ac0986728 doesn't handle the errors, but...

Let us know if you have any questions about that!

> @pitag-ha @panglesd do you want the merge rights by any chance? I don't :) Let's see if @panglesd happens to want them when he's back. Btw, what's the current...

As mentioned in #3, I've just assigned you @Mojoeffect, to this issue, and you, @AryanGodara to #3 to avoid duplicating work. > There are still some Ocaml syntax I'm trying...

Hey @davesnx, have you found out more about when the issue arises? I'm just asking because I've just gone through the open PRs and have seen your PR about this...

@3Rafal, is there anything you'd add?

Currently, the info about cache hits/misses is dumped into the Merlin log-file. I agree that for `merl-an`, it would be simpler if it was added to the Merlin telemetry directly....

Btw, another thing that could be interesting to add is whether the `ocamlmerlin` server is fresh on the request, i.e. whether it's the first request on that server or not....