mirror of
https://github.com/getpaseo/paseo.git
synced 2026-10-31 05:32:58 +00:00
Mohamed Boudra
bd15e40e94
* feat(website): serve paseo.sh in Simplified Chinese
Every page of the website now has a Simplified Chinese version under
/zh-CN: the interface, docs, blog posts, comparison pages, legal pages,
all changelog releases and the homepage mockup. English URLs are unchanged.
The URL alone decides the language. There is no browser-language redirect
and no stored preference, because either would have to redirect the
unprefixed English URLs that people share and search engines index.
Internal links carry the page's language instead, and hreflang alternates
point Chinese search results at /zh-CN.
Translated headings pin the English anchor with {#id}, so section links
work in both languages. content-translations.test.ts fails when a page
has no translation or a translation's headings drift from the English.
Changelog releases and plugin listings without a translation render
whole in English under a notice, so a release never waits on one.
Plugin manifests and the registry gain optional translations and
OVERVIEW.zh-CN.md fields; older clients and registries ignore them.
* feat(website): replace the native language select with an EN/ZH menu
The header showed an OS-native select whose popup did not match the site.
The trigger now shows the language abbreviated (EN, ZH) and opens a menu in
the app's dropdown style that names each language in itself, with its name
in the page language underneath. Rows are real links to the same page in
that language; arrows, Escape, outside presses and taps behave as a menu
button, and the menu keeps itself on screen when a narrow header pushes the
trigger toward an edge.
Also drops the stray space after the full-width comma in the Chinese
homepage subtitle.
* docs(website): translate main's new docs and 0.12.0 release notes
Main added Keep run workspaces to the schedules docs, rewrote plugin icons
around inline SVG, and promoted 0.12.0 with new entries. Bring the Chinese
pages and changelog in line so no section falls back to English.
* fix(server): leave plugin listing translations to the registry
The daemon rejected manifests whose translations the registry would refuse,
so a plugin main installs could fail to load here. Paseo never reads
translations; the registry validates them at publish. Docs now say which
checks are automated at publish and which are human review.
* docs(plugins): describe the registry's final overview translation discovery
* style(server): format manifest test
* test(app): measure sidebar rows one at a time
After a reload the developer error toast appears while expectVerticalOrder
measures every row at once. Each concurrent boundingBox runs the toast
locator handler, and only one of them resumes, so the poll timed out on
every attempt since #7424. Measuring sequentially keeps one action in flight.
* test(app): return sidebar row measuring to main
#7480 hides the developer toast instead of running a locator handler, so
measuring the rows concurrently no longer races it. Reverts 41ac23016.
* test(app): wait for the compact shell before opening compact Changes
The shell survives the breakpoint, so right after the resize the wide
Explorer could still be visible: the test skipped the Explorer toggle and
the tab then disappeared, or toggled at the wrong time. Wait for the
compact-shell marker, as the composer helpers do since #7424.
* docs(website): translate main's plugin file panel docs
* test(app): edit the code font size after the font family remount
A committed appearance change remounts the settings screen through
AppearanceStyleBoundary, and the new form starts from the stored size.
Filling the size before that remount lost the edit in CI.
* docs(website): translate main's client/ui import docs
Follows #7474: one /client/ui entry, StreamedText instead of useRevealedText,
SettingsGroup dropped from the settings table, and the new
'UI imports in v0.13' migration section.
* test(app): wait for the previous layout's file panel picker to leave
After a resize the old layout's picker animates out while the new one is
already mounted, so the Use button matched two elements and the strict
locator failed. Wait for the shell's layout and a single picker first.
3.9 KiB
3.9 KiB
title, description, nav
| title | description | nav |
|---|---|---|
| Hub 活动 | 查看 Hub 如何处理一个事件，区分被过滤和未路由的事件，并排查没有任何反应的触发器。 | 活动 |
Hub 活动
Hub 接受的每个事件都会被记录，无论它是否运行了任何内容。这份记录就是你排查触发器的依据。
在哪里查看
Project → Activity 列出已路由的触发器运行及其执行状态。
Connections → Known unrouted events 是组织级视图，列出已接受但没有启动任何已配置触发器的 Provider 事件。Hub 会记录以下四种原因之一：
| 原因 | 含义 |
|---|---|
no_project_route |
没有为该事件配置项目路由 |
no_trigger_for_source |
没有已配置的触发器处理该事件来源 |
trigger_filters_rejected |
有触发器处理该来源，但它的过滤器拒绝了该事件 |
configuration_unavailable |
无法解析相关的配置或连接 |
我提及了机器人，但什么都没发生
按这个列表逐项排查。
- 事件是否出现在项目的 Activity 中？ 如果没有，请查看 Connections → Known unrouted events，根据其中的原因区分路由、来源、过滤器和配置方面的失败。
- 事件是否出现在任何地方？ 如果没有，说明事件从未到达 Hub。请查看 Provider 自己的投递日志：GitHub 的 App → Advanced → Recent Deliveries，或 Slack 的 Event Subscriptions 页面。然后确认应用订阅了该事件类型。
- 你的用户是否在
from_users中？ 这是最常见的原因。GitHub 使用你的登录名；Slack 和 Discord 使用用户 ID，而不是显示名称。参见查找 Slack ID 和查找 Discord ID。 - 调用是否匹配？ 在 GitHub 上，评论正文中必须出现
contains。在 Slack 和 Discord 上，必须提及机器人，并且提及之后的文本必须以pattern（或其旧别名contains）开头。 - 你以为生效的配置是否真的生效？ Configuration 标签页显示当前生效的版本和上一次同步尝试。推送失败时，旧版本会继续生效。
- daemon 是否已连接？ daemon 离线时派发会失败，并报告
daemon_not_connected。 - 是否运行了但提前停止？ 把这次执行与 step 中编写的
idle_timeout、max_runtime以及 workflow 的max_runtime进行比较。这三个限制都在 workflow 中显式声明。 - 是否运行了但什么都没投递？ 检查 step 的提示词。没有被告知调用
hub.reply和hub.finish_execution的 Agent，可能只在自己的对话记录中回答，而从不回报。参见告诉 Agent 调用哪个工具。
同步失败
Configuration 标签页显示最近的同步状态：
| 状态 | 处理方式 |
|---|---|
| Fetch failed | 该提交中缺少文件，或者 App 无法读取仓库 |
| Invalid | 校验失败，或者配置引用了无法访问的内容 |
| Superseded push ignored | 更新的提交已经移动了分支头；没有任何问题 |
“引用了无法访问的内容”通常是指安装未覆盖的仓库、已被重命名的 daemon，或已不存在的连接 slug。参见 Hub 工作原理。
不会重试
Hub 不会让事件排队。因 daemon 离线而失败的派发会一直保持失败，所以请在 daemon 恢复后重新触发。