dev meeting 2026 07 22

Agenda

• Build Rules (@tim-ats-d)
• Dev Tools (@Sudha247)

Meeting

Attendees: @Alizter, @punchagan, @Leonidas-from-XIV, @Sudha247, @tim-ats-d

Dev Tools (@Sudha247)

• We have the fleshed out requirements here: https://github.com/ocaml/dune/pull/13457/changes.
• Requesting review from other Dune devs
• Sudha to post on Zulip about this
• Would be good to have this agreed upon before starting implementation
• User stories exist and need to be checked against the proposal
• Are there any open design questions?
  • Nothing major

Build Rules (@tim-ats-d)

• Is there a way to check whether a workspace is locked?
  • Editors should not need to care, as the Dune lock is an internal Dune thing
  • Dune should deal talking to running Dune instances via RPC instead of failing
  • dune pkg enabled currently fails when there is another instance
  • There are some workarounds for this
  • VS Code should be launching a watch server
  • Open issues about commands that fail to communicate via RPC
• Questions can be asked on the OCaml Zulip to keep them more public
• Lock already existing exit code inconsistent between commands
  • Not a deliberate decision, it should be consistent
  • Open issues where its inconsistent
  • This should happen less frequently in the future as Dune commands should talk to running instances succesfully instead of failing with lock file issues