bodil / bodil/vscode-blueprint

Couldn't create connection to server on silverblue w/ toolbox-vscode

Open
#3 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
40
Forks
6
PR merge metrics
No merged PRs in 30d

Description

Not sure why this is happening. toolbox-vscode essentially connects to a running toolbox container as the remote, so the command SHOULD be getting run in the container. Instead, I'm getting the following error:

```
[Error - 12:35:47 AM] blueprint-gtk client: couldn't create connection to server.
Launching server using command blueprint-compiler failed. Error: spawn blueprint-compiler ENOENT
```

I can confirm blueprint-compiler is accessible in the container, so I have no idea what is going on.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the failure on Silverblue with toolbox-vscode and inspect how the extension launches blueprint-compiler for the remote toolbox. Compare the compiler's availability inside the container with the environment used by the launched server. Done means the connection succeeds when blueprint-compiler is installed in the container.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.