Skip to content

fix: 按 linyaps 运行路径检查本地数据#10

Merged
guanzi008 merged 3 commits into
masterfrom
fix/linglong-local-data-health
Jun 20, 2026
Merged

fix: 按 linyaps 运行路径检查本地数据#10
guanzi008 merged 3 commits into
masterfrom
fix/linglong-local-data-health

Conversation

@guanzi008

@guanzi008 guanzi008 commented Jun 20, 2026

Copy link
Copy Markdown
Collaborator

变更内容

  • 将玲珑环境管理默认健康检查收敛到 linyaps 运行路径:ll-cli --json list、仓库配置、运行中应用、数据目录权限和磁盘状态。
  • 默认环境分析不再执行底层完整性审计,也不再把 checksum/fsck 差异展示成用户侧“环境异常”。
  • 对话框顶部指标从 OSTree 改为 本地数据,问题列表区分“玲珑本地数据不可用”和“玲珑本地数据检测失败”。
  • 显式修复动作仍保留受控底层修复与重拉复验,但用户侧文案统一表达为“玲珑本地数据修复”。
  • 修复 release notes deterministic changelog 在 mawk 下从 0、 起始的问题,避免 PR CI release smoke 失败。
  • 更新 docs/21-linglong-environment-management.mdAGENTS.md,记录默认健康模型和后续实现约束。

背景

基于 linyaps 源码和 uuu Loong64 环境排查,完整性审计可能在 bare-user-only 本地存储模式下报 checksum 差异,但 ll-cli --json repo showll-cli --json listll-cli --json ps 仍可正常执行。默认环境分析应跟随 linyaps 自身运行逻辑,而不是把底层审计结果直接暴露为基础环境异常。

本 PR 第一次 CI 中 Run release CLI smoke test 失败,定位为 awkitems[++item_count] = item_count ... 左右侧求值顺序不一致,CI 的 awk 会生成 0、 起始编号;已改为先递增再赋值。

验证

  • /home/hao/Flutter/flutter-stable/bin/flutter test test/unit/data/repositories/linglong_cli_repository_impl_command_test.dart test/unit/application/services/linglong_environment_management_service_test.dart test/unit/application/providers/linglong_environment_management_provider_test.dart test/widget/presentation/widgets/linglong_environment_management_dialog_test.dart test/widget/presentation/pages/setting_page_test.dart
  • /home/hao/Flutter/flutter-stable/bin/flutter analyze
  • FLUTTER_ROOT=/home/hao/Flutter/flutter-stable bash build/scripts/release-cli-smoke-test.sh
  • FLUTTER_ROOT=/home/hao/Flutter/flutter-stable bash build/scripts/nightly-cli-smoke-test.sh
  • bash build/scripts/validate-release-workflow.sh

@guanzi008 guanzi008 merged commit 90fcd7b into master Jun 20, 2026
1 check passed
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