You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should be possible to run _build/default/bin/main.exe build --watch from the dune repository, and then in a second terminal run _build/default/bin/main.exe rpc ping and have the second command return immediately.
Actual Behavior
The ping command hangs forever. I've only been able to reproduce this in the dune repository. Running a freshly-built dune binary in other projects seems to work as expected.
Reproduction
Compile dune
Run _build/default/bin/main.exe build --watch from the root of the dune directory
In a second terminal, run _build/default/bin/main.exe rpc ping also from the root of the dune directory.
Specifications
Version of dune (output of dune --version): 82c670e
Version of ocaml (output of ocamlc --version): 4.14.1
Operating system (distribution and version): NixOS
This #7418 removes threads for RPC altogether. Does it fix the issue for you?
I don't see the problem on that PR branch.
I tried reproducing on a different machine in my home and I couldn't. It could be related to the fact that my main machine (where I see the problem) has a relatively large number of cores (32).
Expected Behavior
It should be possible to run
_build/default/bin/main.exe build --watch
from the dune repository, and then in a second terminal run_build/default/bin/main.exe rpc ping
and have the second command return immediately.Actual Behavior
The ping command hangs forever. I've only been able to reproduce this in the dune repository. Running a freshly-built dune binary in other projects seems to work as expected.
Reproduction
_build/default/bin/main.exe build --watch
from the root of the dune directory_build/default/bin/main.exe rpc ping
also from the root of the dune directory.Specifications
dune
(output ofdune --version
): 82c670eocaml
(output ofocamlc --version
): 4.14.1Additional information
The first commit with this behaviour is 8bea7ea
The text was updated successfully, but these errors were encountered: