Repository navigation
diag(shell): 标题事件 invalid text 带上字节 (#57) - #282
Merged
Merged
Conversation
The candidate event path only said invalid text; it now carries the kind, the length and the first bytes so the payload shape is identifiable.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
内容
按 #57 的未知项("旧失败事件的 kind/length/callsite 全是 null"),给候选事件路径的标题事件加有界诊断:
实现:
shell.cpp的route_terminal_events()里case 2捕获utf16()的异常,记录kind、字节数与十六进制前缀后再抛出。为什么
原始失败只有一句
invalid text(来自presentation/render.hpp的require(n != 0, ...)),无法判断是空串、代理对截断还是完全非 UTF-8 的 OOB 数据。加上这三项后,下一次复现即可定位到具体载荷形状。验证
termforge_shell构建通过(候选构建路径未变,tip 只在异常分支触发)。边界
Refs #57