.elp.toml file for erlang.mk projects?

Questions / Help
,
1

We’re using erlang.mk. I’ve just moved from using Erlang LS to ELP, in Visual Studio Code.

My editor is now a sea of yellow squiggles, because it can’t find my dependencies. For example, it doesn’t recognise cowboy_req:set_resp_headers/2 and so on.

Does anyone have a working example of ELP’s .elp.toml file for use with erlang.mk projects? I found one in the RabbitMQ repo, and hacked on it, thus:

[build_info]
deps = "deps/*"

But after doing this, ELP still warns about (e.g.) cowboy, plus it’s forgotten about built-in OTP functions, such as string:uppercase/1.

2

Hi @rlipscombe

The full documentation for the build_info field is available here:

An extensive example is the one from OTP itself:

If you could share a (maybe minimized) version of the repo and/or the erlang.mk config, I can help you get started. What did the erlang_ls.config file looked for the repo?

3

This is what I use for a poorly structured umbrella project:

[build_info]
apps = [
    "apps/*",
    {"name" = "a_bad_app_that_we_have_on_the_root_folder", "dir" = ".", "src_dirs" = ["src"], "include_dirs" = ["apps/*/src", "apps/*/include"]}
    ]
deps = [
    "deps/*"
    ]

I use kerl to manage Erlang and OTP24, in particular, for this project.

ELP finds OTP functions and deps with no issue in VSCode. There are other things I’m missing, mostly because I’m on OTP24 (like eqwalizer support, I believe)… but the rest works… mostly fine (with a lot of warnings, but no blocking problems).

1 Like
4

And since I’m pretty sure @robertoaloi will ask me about the warnings… This is one example that repeats a lot:

Panic context:
> 
request: textDocument/codeLens CodeLensParams {
    text_document: TextDocumentIdentifier {
        uri: Url {
            scheme: "file",
            cannot_be_a_base: false,
            username: "",
            password: None,
            host: None,
            port: None,
            path: "/path/to/my_module.erl",
            query: None,
            fragment: None,
        },
    },
    work_done_progress_params: WorkDoneProgressParams {
        work_done_token: None,
    },
    partial_result_params: PartialResultParams {
        partial_result_token: None,
    },
}

read '<unnamed>' panicked at /Users/runner/work/erlang-language-platform/erlang-language-platform/crates/erlang_service/src/lib.rs:366:14:
failed sending request to parse server: "SendError(..)"
stack backtrace:
   0: __rustc::rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::result::unwrap_failed
   3: <elp_ide_db::RootDatabase as elp_ide_db::erl_ast::AstLoader>::load_ast
   4: salsa::derived::slot::Slot<Q,MP>::read_upgrade
   5: <DB as elp_ide_db::erl_ast::ErlAstDatabase>::module_ast::__shim
   6: <elp_ide_db::RootDatabase as elp_ide_db::common_test::CommonTestLoader>::check
   7: salsa::derived::slot::Slot<Q,MP>::read_upgrade
   8: <DB as elp_ide_db::common_test::CommonTestDatabase>::ct_info::__shim
   9: elp::handlers::handle_code_lens
  10: <F as threadpool::FnBox>::call_box
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
[Error - 10:28:22] Request textDocument/codeLens failed.
  Message: internal error
  Code: -32603
5

@elbrujohalcon do you have a small repro for this one? It would help me fixing it.

6

Sorry, but no. It’s a huge repo, with tons of particular customizations and zero chance of sharing anything from it. It’s super private.

7

This seems to work:

[build_info]
apps = [{name = "my_app", dir = "."}]
deps = "deps/*"

Kinda odd that you need to specify the app, even though this isn’t an umbrella. Maybe ELP needs the name for something?

It doesn’t like hackney, though – because of the way that hackney:post/{1,2,3,4}, etc. are defined with a macro, I’m guessing.

2 Likes