Cloud compute errors say "sandbox" instead of workspace
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
Research direction
The five user-facing error strings are in services/compute/index.ts at lines 89, 114, 191, 197 and 304. Check docs/terms.md for the approved term (workspace) and the app's action names, such as Start compute. Reword each message to use those terms, changing only the text and not any stored format or control flow. Done when none of the five messages says "sandbox" and the wording matches the glossary.
Written by the indexing model from the issue text.
Description
The cloud compute service's errors call the workspace a "sandbox". docs/terms.md calls it the channel's workspace (a container in the pilot). These messages reach people through the app's "Cloud compute" refusals, so the wrong term shows up in the UI.
services/compute/index.ts:
- L89
The sandbox is stopped - L114
Sandbox did not become ready in 120 seconds - L191
Sandbox is already running; use resize to change its size - L197
The sandbox was lost without a checkpoint; refusing to create an empty replacement - L304
The sandbox is stopped; use start to restore it
Reword them in terms of the workspace and the app's actions. For example, "The cloud workspace is stopped; use Start compute to restore it." Rewording these messages doesn't change any stored format.
Found while writing up the cloud compute part of the automated study.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
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 githubnext/ace2
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
githubnext/ace2#487 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
githubnext/ace2#486 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
githubnext/ace2#459 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
githubnext/ace2#442 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 40/100
githubnext/ace2#440 ·
Similar issues
-
area:plugins enhancement platform:vscode
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
anthropics/claude-code#103166 ·
Maintainers usually reply within 1 day
-
check:failed streams:add
Difficulty 1/5 Under an hour Newbie friendliness 90/100
iptv-org/iptv#55744 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
jitsi/jitsi-meet#18021 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
spec: discovery input example can contain multiple aliases for one parameter, with no canonical oneOpen
Difficulty 1/5 Under an hour Newbie friendliness 95/100
x402-foundation/x402#3841 ·
Maintainers usually reply within 1 day