That integration can be extremely interesting.
Can you please describe some typical user-stories and interactions that could leverage the DAP support? Basically, what gets debugged? The build process or the resulting app?

Our intention here is to provide a working DAP implementation which can later be used from Metals. Our end goal here is to add the capability of launching main classes and test suites from LSP client (e.g. vscode) using code lenses (basically buttons above the main class or test suite like in IntelliJ, if you are not familiar with the term)

what gets debugged?

That depends on the DebugSessionParams.dataKind field. Currently we are planning a support for jvm main classes and various jvm test suites. For more technical information you can follow a (rather lenghty) thread in this bloop PR.

If you have more questions then, if the are related to the BSP let's continue the discussion here. Otherwise, don't hesitate to ask them in the linked bloop PR.

Would you mind looking at the reason why the CI is failing?

Fixed in #100, I will rebase the PRs after it is merged

@mickaelistria As Marek says, feel free to drop by the Bloop PR or our gitter channel https://gitter.im/scalacenter/bloop if you want to know more about the details, we're happy to elaborate on how we envision the DAP<>BSP integration.

@marek1840 Ready to merge, feel free to press the merge button when you rebase 👍