AstrBot-Desktop/src-tauri
YokiiroBW 7a6877d7cc
一些检测仍在等待运行
ci / Portable quality checks (push) Waiting to run
ci / Windows Tauri build (push) Waiting to run
fix(astrbot): fetch chat attachments from the paths this server serves
The request trace showed the app talks to 192.168.31.210:26185, not the
host I had been probing, so the endpoint list I read from a dashboard
bundle belonged to a different AstrBot build. This server's own bundle
resolves a chat attachment as:

  /api/chat/get_attachment?attachment_id=...   when an id is known
  /api/chat/get_file?filename=...              otherwise

There is no /api/v1/files at all here. Asking for it returned AstrBot's
"404 Not found" page under HTTP 200, which is why the status check
passed it through as a successful download of an undecodable file.

Try each address in turn — the stream supplies a file name in the media
frame and an id in the frame after, and different builds expose
different paths. Because an unknown path answers 200 with that text
page, a candidate counts as found only when the bytes are recognisably
an image; the status alone proves nothing here. Trying all three also
recovers attachments in existing history, whose markers hold the id
rather than the name.

Refs: N-6.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 03:24:11 +08:00
..
capabilities fix(tauri): grant the window controls the permissions they call 2026-07-27 01:19:42 +08:00
icons feat(p00): add Tauri desktop spike foundation 2026-07-18 20:34:47 +08:00
src fix(astrbot): fetch chat attachments from the paths this server serves 2026-07-27 03:24:11 +08:00
tests fix(tauri): grant the window controls the permissions they call 2026-07-27 01:19:42 +08:00
build.rs feat(p00): add Tauri desktop spike foundation 2026-07-18 20:34:47 +08:00
Cargo.toml feat(p00): add Tauri desktop spike foundation 2026-07-18 20:34:47 +08:00
tauri.conf.json fix(tauri): allow blob images in production csp 2026-07-26 22:28:35 +08:00