Plugin debugger does not like ecto-sqlite3 at all.

[jdmarshall]

Describe the bug

can't debug ecto tests in a project that uses ecto-sqlite3, but can with postgex

'mix test' runs to completion from the run menu in both cases, but not debug.

To Reproduce

I created this project following the ecto getting started guide in the hexdocs, only diverting to use ecto-sqlite3 instead of postgrex.

https://github.com/jdmarshall/ecto_issues/tree/trunk

Then run with latest plugin, with 1.18.2 compiled for erlang 26 (27 fails for entirely different reason

Expected behavior Debugging should run.

Screenshots If applicable, add screenshots to help explain your problem.

Logs

This repeats in a loop:

15:35:16.533 [error] :gen_statem #PID<0.22834.0> terminating ** (RuntimeError) connect raised ErlangError exception. The exception details are hidden, as they may contain sensitive data such as database credentials. You may set :show_sensitive_data_on_connection_error to true when starting your connection if you wish to see all of the details :erlang.nif_error/1 (exqlite 0.29.0) Elixir.Exqlite.Sqlite3NIF.erl:21: Exqlite.Sqlite3NIF.open/2 (exqlite 0.29.0) Elixir.Exqlite.Connection.erl:540: Exqlite.Connection.do_connect/2 Queue: [internal: {:connect, :init}] Postponed: [] State: Exqlite.Connection Callback mode: :handle_event_function, state_enter: false

Desktop:

• OS: MacOS Sonoma
• Version 14.7.4 (23H420)

Erlang:

• Installer asdf
• Version 26.2.5.8

Elixir:

• Installer asdf
• Version 1.18.2-otp-26

Plugin:

• Version 20.0.1

Additional context Add any other context about the problem here.

[jdmarshall]

@KronicDeth I think the main issue here is that the README could use a section in the debugger to warn that you probably need to ignore NIFs in order to get the debugger to run. Someone else have me a heads up about this.

Possibly the error could use a reminder as well.