Skip to content

"{file} is not available" is an unacceptable error message when localfs = default (false) #513

@dmlambo

Description

@dmlambo

Problem: OTB experience for attaching to a Ruby program and setting a breakpoint is broken.

I just spent 5 hours sifting through VS Code source, and finally stumbling upon a closed issue in this repo that was tangential to mine which solved my problem.

The default attach configuration does not include "localfs": true, which is not in and of itself a problem. The problem is when this is false and the files are indeed local (that is, when all paths in logging are valid), the error message reads:

2025-11-29 22:49:47.181 [error] [Window] {file} is not available: CodeExpectedError: {file} is not available

The stack it returns is of course useless as it is the result of an RPC, and the only way to get more info is with, perhaps, "showProtocolLog": true.

There is no feedback to say that a breakpoint will not be hit. There is no remediation, no calls to action, and no otherwise useful logging.

That said, I do appreciate the work you've done, and indeed everything works now. But my lord if I didn't have a bunch of experience and patience, I would have just assumed the extension was broken.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions