Skip to content

Container breakpoints occasionally marked invalid (but still hit) #144

Closed
@JacksonKearl

Description

@JacksonKearl

Using vscode-remote-try-node container:

Set breakpoint in the handler for:

const app = express();
app.get('/', (req, res) => {
	console.log("hello");
	res.send('Hello remote world!\n');
});

It will (sometimes) get shown as unbound. However, upon navigating to the page it will still be hit. I was not able to repro outside of a container.

Metadata

Metadata

Assignees

Labels

bugIssue identified by VS Code Team member as probable bugupstreamverifiedVerification succeeded

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions