Trace inspector version check breaks use of this extension in container environments

[colbymelvin]

Hi there, I wanted to report an issue I came across trying to attach a debugger to a running Rails process after upgrading this plugin to v0.2.1.

I'm unable to start a debugger with a Trace Inpsector failed to start because of failing to check version exception being thrown each time. I noticed that after the initial work to integrate Trace/Record inspector, there was a followup to disable it if the debug gem's version is less than 1.8.0.

That version check is raising an exception for me because it issues a shell command on the host machine. This breaks in a container environment where rdbg isn't installed on the host machine and is instead installed on a container image.

At the moment, I'm working around this by having an rdbg executable in my path that catches any and all rdbg commands, including the rdbg --version issued by getVersion, and runs them in the container, returning the output.

System information

(host machine)
macOS 13.2.1
VSCode 1.79.2

(container environment)
Docker 4.17.0
Alpine Linux 3.18.0
rdbg 1.8.0
Ruby 3.2.2
Rails 7.0.5

[ono-max]

Sorry for bothering you. I believe that you can solve this problem by disabling Trace Inspector. Can you try it?