Skip to content

chore(subos): silence storage-dormant hint on shell-level entry#294

Merged
Sunrisepeak merged 1 commit into
mainfrom
chore/silence-storage-dormant-hint
May 15, 2026
Merged

chore(subos): silence storage-dormant hint on shell-level entry#294
Sunrisepeak merged 1 commit into
mainfrom
chore/silence-storage-dormant-hint

Conversation

@Sunrisepeak
Copy link
Copy Markdown
Member

Summary

  • 注释掉 warn_storage_dormant_on_shell_() 里的 stderr 提示
  • 不删函数 / 不动调用点,后面想换更清楚的措辞时可以原地替换

起因

当前提示:

[xlings] storage=image is sandbox-only; entering shell-level (use --sandbox to activate)

两个问题:

  1. 措辞歧义use --sandbox to activate 在中英文里都容易被读成动词 vs xlings subos use 命令名;activate 没说激活的是 storage 隔离。
  2. 噪音 — 每次 shell-level 进 image/tmpfs subos 都打一次,用户知道布局后纯打扰。

状态

Draft — 暂不合入,先放着观察一下要不要顺手做更彻底的 UX 改造(一次性提示 / 仅在 --verbose 下打 / 重写措辞)再决定合或者重写。

Test plan

  • xlings subos use <image-subos> 不再打出 hint
  • xlings subos use <image-subos> --sandbox 行为不变
  • xlings subos use <shared-subos> 行为不变(原本就 early-return)

The hint "[xlings] storage=X is sandbox-only; entering shell-level
(use --sandbox to activate)" had two UX issues:

- Ambiguous wording: "use --sandbox to activate" reads as either the
  verb or the `xlings subos use` command name; "activate" doesn't say
  what gets activated (the storage isolation).
- Noisy: fires on every shell-level entry into an image/tmpfs subos,
  even after the user already knows the layout.

Comment out the println for now; the call site
(warn_storage_dormant_on_shell_) is kept so we can drop in a clearer
one-time / opt-in form later without restructuring the callers.
@Sunrisepeak Sunrisepeak marked this pull request as ready for review May 15, 2026 07:46
@Sunrisepeak Sunrisepeak merged commit b5cc1e1 into main May 15, 2026
3 checks passed
@Sunrisepeak Sunrisepeak deleted the chore/silence-storage-dormant-hint branch May 15, 2026 07:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant