Issues From First Run Inside Dev Container
Maintainers usually reply within 1 day
@thesiti92 is already working on this.
Since Oct 1, 2026.
Assessment
This issue has not been assessed yet.
Description
Background: I use NixOs as my linux distro so most apps need some nix specific tweaks to get working. It is often easier to launch them from containers with the appropriate permissions. I usually do this and it works fine. That is what I did in this case
Setup
whiteboard app launch fails, but running review-desktop directly succeeds and spawns the window (side: review-desktop should probably be documented somewhere)
root@📦:/workspaces/languna (master)$ whiteboard app launch
Error: Could not launch Whiteboard with the Desktop-managed bundle at "/usr/share/whiteboard/whiteboard": the launch process exited on SIGTRAP. Open Whiteboard once, then run `whiteboard app launch` again. A sandboxed agent must run it outside the sandbox.
at launchFailure (file:///usr/share/whiteboard/resources/app/review-runtime/dist/cli-runner-CFIWhBbX.js:667:25)
at assertSuccessfulLaunchCompletion (file:///usr/share/whiteboard/resources/app/review-runtime/dist/cli-runner-CFIWhBbX.js:671:8)
at Object.runReviewAppLaunch (file:///usr/share/whiteboard/resources/app/review-runtime/dist/cli-runner-CFIWhBbX.js:570:4)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async Command.launchApp (file:///usr/share/whiteboard/resources/app/review-runtime/dist/cli-runner-CFIWhBbX.js:4917:17)
at async Command.parseAsync (/usr/share/whiteboard/resources/app/review-runtime/node_modules/commander/lib/command.js:1122:5)
at async runReviewCli (file:///usr/share/whiteboard/resources/app/review-runtime/dist/cli-runner-CFIWhBbX.js:5119:3)
at async file:///usr/share/whiteboard/resources/app/review-runtime/dist/cli.js:13:41
Trace/breakpoint trap (core dumped)
root@📦:/workspaces/languna (master)$ review-desktop -h
[1001/105636.877838:FATAL:electron/shell/app/electron_main_delegate.cc:219] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
Trace/breakpoint trap (core dumped)
root@📦:/workspaces/languna (master)$ review-desktop --no-sandbox
Attempted First Review
The review started well and worked with my codex agent, but I ran into these issues
- Cannot work with my submodule
[main 2026-10-01T11:06:30.413Z] [Review server] [Review API] GET /reviews-api/c0b24ab9-7bb3-4d23-9a38-06003ccdcd5b/progress failed: Error: Cannot count lumar: structural diffs currently require regular text files (not symlinks or submodules)
- I tried to close the vscode window it spawns and it crashed the whole program. I was unable to interact with or close any spawned windows after that. Relevant logs:
[main 2026-10-01T11:07:15.827Z] CodeWindow: detected unresponsive
[22250:1001/110718.372160:ERROR:content/browser/browser_main_loop.cc:274] GLib-GObject: ../../../gobject/gsignal.c:2685: instance '0x149c036890d0' has no handler with id '1893'
- Sending SIGINT did not result in a graceful shutdown, instead got
Segmentation fault (core dumped)
Desired Behavioral Changes
It would be nice if it used my currently installed and opened vscode window, rather than open a new vscode instance that seems to be bundled with the app. Maybe this is related to running the app inside a container and I need to install it on my system in a nix flake though, but then it would lose access to my codex agent and my container environment
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 145
- Avg merge
- 16h 28m
- Merged PRs (30d)
- 553
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from devdotfast/whiteboard
-
Privacy page missingPossibly taken @sidkmenon claimed this 15 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 72/100
devdotfast/whiteboard#1091 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 Half a day Newbie friendliness 42/100
devdotfast/whiteboard#1429 · 2 comments ·
Maintainers usually reply within 1 day
-
Native BYOK support for visual reviews and Ask without an external coding agentPossibly taken @thesiti92 claimed this 9 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
devdotfast/whiteboard#1218 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Add Kotlin as an optional language group in Whiteboard DesktopPossibly taken @sidkmenon claimed this 14 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
devdotfast/whiteboard#1092 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
devdotfast/whiteboard#1090 · 1 comment ·
Maintainers usually reply within 1 day
All issues in devdotfast/whiteboard
Similar issues
-
e2e-failure ready-to-code
Difficulty 1/5 Under an hour Newbie friendliness 82/100
redhat-developer/rhdh-plugin-export-overlays#4616 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
ai-handle
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nextlevelbuilder/dewee-web-v2#73 ·
Maintainers usually reply within 1 day
-
backend bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
PoCInnovation/Distribox#255 ·
Maintainers usually reply within 1 day