fix: harden wiki delivery and leaderboard performance
This commit is contained in:
1 parent
0c5e2e8cb0
commit
9f29ecae9e
28 files changed
+616
-68
No files matched your search
@@ -802,8 +802,12 @@ database leases; searches use revision-checked per-knowledge-base LRU snapshots
|
||||
after the full-library readiness gate succeeds. Knowledge-base owners can click
|
||||
**手动向量化** in Wiki management (`POST
|
||||
/api/llmwiki/knowledge-bases/{id}/vectorize`) and follow its status at
|
||||
`GET /api/llmwiki/knowledge-bases/{id}/wiki-index-status`. Existing chunk
|
||||
citations remain readable while all new retrieval citations open Wiki pages.
|
||||
`GET /api/llmwiki/knowledge-bases/{id}/wiki-index-status`. The response includes
|
||||
aggregate `progress` plus a `pages` list with every Wiki page's index state,
|
||||
vector-section count, timestamps, and last error. The management page renders
|
||||
the percentage and labels each article as 已向量化 / 待向量化 / 失败, so it is
|
||||
clear exactly what is searchable. Existing chunk citations remain readable
|
||||
while all new retrieval citations open Wiki pages.
|
||||
|
||||
The frontend labels these results simply as **Wiki** references; provider-brand
|
||||
wording is intentionally hidden from user-facing labels and status text. Clicking any
|
||||
@@ -826,6 +830,29 @@ left. It reconstructs hierarchy from `parent_slug`, `wiki_path`,
|
||||
page, and switches directory entries through the same lightweight reader route
|
||||
without mounting the WeKnora iframe.
|
||||
|
||||
All generated SPA deep links preserve the deployment document path (for
|
||||
example `/web/`) before the `#` route, including Q&A references and Wiki index
|
||||
links. Protected Wiki images no longer render from temporary browser `blob:`
|
||||
URLs. Public images use the published file proxy directly; private images first
|
||||
obtain a 24-hour signed capability and then load through
|
||||
`GET /api/public/llmwiki/files/{token}` with a real HTTP URL and inline
|
||||
filename, allowing zoom, new-tab viewing, and browser Save As without exposing
|
||||
the user's bearer token.
|
||||
|
||||
## Leaderboard query and schema startup safety
|
||||
|
||||
The leaderboard excludes scheduled runs with indexed correlated `NOT EXISTS`
|
||||
checks. Tool metrics no longer outer-join the full `runs` table merely to
|
||||
recognize legacy scheduler messages. New databases receive dimension-aware
|
||||
analytics indexes from ORM metadata; existing large MySQL deployments should
|
||||
run `scripts/sql/leaderboard_indexes_mysql.sql` during a low-traffic window so
|
||||
index creation never delays application startup.
|
||||
|
||||
Startup Alembic migrations now have one unambiguous head. The historical
|
||||
duplicate `20260821_01` identifier is repaired by unique fixed-question
|
||||
revisions and the `20260825_01` merge revision, which also fills the
|
||||
report-structure column for databases stamped by either old variant.
|
||||
|
||||
Published knowledge bases also have a login-free, chrome-free reader at
|
||||
`/#/embed/knowledge/{mapping_id}` for direct third-party iframe use. With no
|
||||
`wikiSlug`, it selects the Wiki **索引** page first (recognized by title, page
|
||||
|
||||
Reference in new issue
Block a user