Vincent Bernardoff

Great, thanks. @mfp Could you make a new OPAM release please?

Ok. The release cycle is so fast for this project, anyway. Version 7 is already going out. Thanks.

Any update on this? This is a common use case.

In a few months??

Same here ```[server-reply] (id:41) ERROR Mon Nov 16 00:27:43 2020: (:jsonrpc "2.0" :id 41 :error (:code -32603 :message "Could not find parameter locations")) [internal] (id:41) ERROR Mon Nov 16 00:27:43...

In the sense that `alcotest` (apparently) uses exceptions when failing tests and uses the exception to display the problem (i.e. the function returned x instead of y in the case...

https://tools.ietf.org/html/rfc6585

@seliopou @sazarkin What do you guys want to do with statuses from newer RFCs? Merge them, or just continue to use ``Code x`? I'm fine with both solutions, but please...

It was also blocking upgrade to Core v0.15, which caused other problems for my use cases…

@seliopou Could we merge this? And also release a new version. It blocks at least one project of mine to be installable directly with opam dependencies.