Skip to content

fix(buddy): 完善云备份加载失败时的状态恢复与错误提示 - #611

Merged
shanyuhai123 merged 3 commits into
useLexora:masterfrom
QAyong:upstream-pr/settings-load-error-recovery
Nov 12, 2026
Merged

shanyuhai123 merged 3 commits into
useLexora:masterfrom
QAyong:upstream-pr/settings-load-error-recovery

Conversation

@QAyong

@QAyong QAyong commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

背景与关联 / Context and related issue

云备份初次读取状态失败后缺少恢复入口。本 PR 仅处理云备份,不修改模型加载错误的展示与恢复路径。

主要改动 / Changes

  • 状态读取失败时显示不可用状态和重试入口,保持备份开关禁用。
  • 重试复用同一条提示;恢复、收到状态更新或离开页面时清理提示。
  • 增加桌面回归,覆盖重复失败、重试恢复、状态事件恢复,以及备份保持关闭。

验证 / Verification

  • 本地 lint、类型检查及构建通过。
  • 6378 项测试通过,33 项跳过;云备份桌面回归通过。
  • 隔离环境注入状态读取失败,生成浅色、深色失败与恢复截图;未连接真实远端备份服务。

兼容与风险 / Compatibility and risks

不涉及数据格式或配置变更,不会因重试读取状态而开启备份。

界面变更 / UI changes

仅调整云备份状态读取失败时的提示和重试交互。


<template>
<div class="desktop-models-settings gap-[1.8rem]">
<NAlert v-if="providerSettings.modelProviderError.value" type="error" :show-icon="false">

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

这个有截图效果么,感觉这边用 message 样式比较统一一点

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

目前暂时没有这是前面提交附带的,主要是mcp这个一直转圈我是实际遇到的,然后这个是AI附带检查出来的

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

那我本地 mock 看下效果吧,有个 CI 问题顺带处理下?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

模型加载失败的这个提示来的有点奇怪,不应有这种交互展示。要么是模型直接失败,或者是某一条,将会移除这部分。

@shanyuhai123 shanyuhai123 changed the title fix(buddy): 完善云备份与模型设置页加载失败时的状态恢复与错误提示 fix(buddy): 完善云备份加载失败时的状态恢复与错误提示 Nov 12, 2026
@shanyuhai123
shanyuhai123 merged commit 2173712 into useLexora:master Nov 12, 2026
10 checks 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.

2 participants