release-candidate / vscode-ocaml-expect-inline Goto Github PK

When there is a dune build in watch mode, the extension should instead do an rpc request to dune rather than run its own dune.

Hi,

Running the tests in the dune repo for example doesn't quite work:

There appears to be a lot of flickering and it isn't obvious what is actually happening.

For reference, I have the OCaml platform extension also installed.

It would be nice if this extension used dune rpc also so that it can connect to a dune already in watch mode. At the moment, Dune disallows multiple dune processes in the same project due to one of them acquiring a lock.

When we have diffs in error messages they are simply rendered as plain text:

It would be nice if they were rendered diffs.

Describe the bug
The VSCode's Testing tab does not show anything

My dune project's directory has this directory hierarchy (.ml files are omitted):

ProjectName
- dune-project
- ProjectName.opam
- bin
  - dune
- lib
  - dune
- test <- this is just a dummy directory, containing nothing
  - dune

I think dune is correctly configured because my VSCode can successfully typecheck variables and highlight compilation errors from .ml files.

To Reproduce
Steps to reproduce the behavior:

1. Install the plugin and wait
2. Click the 'Testing' tab on the left

Expected behavior
A list of tests are shown

Screenshots

Logs

If applicable, add logs of the extension (Output of Expect and Inline Tests), the Extension Host (Ouput of Extension Host) and Window (Output of Window).

I would like to report, but where can I find these?

Example OCaml project

Environment (please complete the following information):

• Version of the extension: v0.2.0
• Version of VS Code: 1.76.1
• OS: [e.g.Linux] WSL2, Ubuntu

Additional context

When the extensions are waiting for Dune to run the tests, it appears that they are waiting for the lock to be released. However when pressing cancel the tests are not cancelled.