chore: validate against mcpp 2026.8.27.2 — the engine that fixes #516 - #266
Merged
Conversation
MCPP_VERSION 2026.8.27.1 -> 2026.8.27.2. #263 moved this pin seventeen versions forward, to 2026.8.27.1. That is the version PR #260 is failing on, and the failure is not #260's: error: internal: unhandled exception: No mapping for the Unicode character exists in the target multi-byte code page. three times, in `workspace (windows default 0/2)` and `1/2` — one per httplib example. It is mcpp-community/mcpp#516: on Windows `path::string()` converts through the process ANSI code page and throws for a name that code page cannot spell, and `is_excluded_walk_dir` narrowed a directory name on the first line of the glob walk. cpp-httplib ships `test/www/<CJK>Dir/`, and the `include_dirs = { "*" }` convention walks the whole extracted tarball. Fixed in mcpp 2026.8.27.2 (mcpp-community/mcpp#517), released and mirrored on both hosts, with xim-pkgindex's `latest` pointing at it.⚠️ RE-RUNNING #260 WITHOUT THIS BUMP PROVES NOTHING. Its CI would fetch 2026.8.27.1 — the version that still carries the defect — and reproduce the same three errors. That is a re-confirmation of the bug, not a test of the fix. Attribution first: the failing job's log was read and it is #516's message verbatim, not some other Windows problem wearing the same red. Keeping #263's caution in force: a red at this pin can come from the engine change or from what accumulated across the versions this repository never ran against, and a one-sided reading cannot tell them apart.
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.
MCPP_VERSION2026.8.27.1 → 2026.8.27.2(单点,validate.yml:166)。为什么现在
#263 刚把这个 pin 前移了十七个版本到
2026.8.27.1。那正是 PR #260 正在失败的版本,而那个失败不是 #260 的问题。
读了失败 job 的日志,是这一句,出现三次(对应三个 httplib 用例),
落在
workspace (windows default 0/2)与1/2:这是 mcpp-community/mcpp#516:Windows 上
path::string()经进程 ANSI 代码页转换,遇到该代码页拼不出的字符就抛;而
is_excluded_walk_dir在 glob walk 的第一行窄化目录名。cpp-httplib 带了
test/www/<CJK>Dir/,而include_dirs = { "*" }的字面前缀为空,会遍历整棵解压树。
已在 mcpp 2026.8.27.2(mcpp-community/mcpp#517)修复,发布并在 GitHub / GitCode
两个 host 上镜像完毕,
xim-pkgindex的latest已指向它(三个平台表都已 bump,四个 sha256 与本地重算值逐一相同)。
它的 CI 会去取
2026.8.27.1—— 仍然带着缺陷的那个版本 —— 然后复现同样的三条错误。那是把 bug 再确认一遍,不是验证修复。
归因是先做的:失败日志读过了,是 #516 的原话,不是别的 Windows 问题穿着同一件红衣服。
保留 #263 的告诫
这个 pin 上的红有两种可能来源:引擎这次的改动,或者本仓从未跑过的那些中间版本积累下来的东西。
单侧读数分辨不了它们。本次只动一个数字,不夹带其他改动,正是为了让下一次红可归因。