[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f3pi418ahzmqmc":3},{"slug":4,"category":5,"publishedAt":6,"titleZh":7,"titleEn":8,"summaryZh":9,"summaryEn":10,"models":11,"hardwares":12,"bodyZh":13,"bodyEn":14,"sourceName":15,"sourceUrl":16,"updatedAt":17},"club3090-numeric-locale-measurement-fix-2026-11-04","RUNTIME","2026-11-03T23:04:42.478Z","社区测量工具修正小数解析：10.02GB 为何会被写成 8,00GB","Community measurement tooling fixes locale parsing: why 10.02 GB became 8,00 GB","club-3090 新合并修复显示，西班牙语数字区域设置配合 mawk 可截掉小数。修正的是报告解析与打印，不是引擎突然少占了内存；其他语言环境的日志也要检查。","A newly merged club-3090 fix shows how a Spanish numeric locale with mawk can truncate fractions. This corrects reporting and parsing, not actual engine memory use.",[],[],"同一份启动日志，数字解析错误就能把内存规模写错。本次窗口内，club-3090 合并 PR #1930，统一脚本的数字区域设置。PR 于 11 月 3 日 22:08 UTC 合并，给出了真实 es_ES.UTF-8 环境下的复现与回归检查。这是一条测量工具修复，不是新的硬件速度测试。\n\n1. 错误如何发生。原文三张卡的 host-backed 专家数据分别为 1.65、4.56、3.81GB，合计 10.02GB。作者发现，在使用小数逗号的区域设置下，mawk 将这些带点字符串按整数部分解析，得到 1、4、3，再打印成“8,00 GB”。原文还展示了 mem_total_gib=188,5。单位看似完整、数值也不离谱，但报告已经与启动日志不一致。\n\n2. 修复改了什么。提交在执行数值工作的脚本中强制 LC_NUMERIC=C，并处理优先级更高的 LC_ALL：先把原值迁移到其他区域类别，再取消 LC_ALL，避免它继续覆盖数字设置。只改一处启动器不够，因为报告工具会把自己的输出重新读回，任何中间环节留下逗号都可能污染后续解释。\n\n3. 如何判断影响。上游自报新增检查覆盖 LANG、LC_NUMERIC、LC_ALL 三种入口；在具备真实西班牙语 locale 与 mawk 的环境验证和为 10.02GB，相关测试集合为 35\u002F35。作者同时说明，更大范围测试提前停止，不能写成全套全部通过。这些是维护者的修复与测试自报，不是 AraoAI 独立执行的结果。\n\n使用者先核对原始日志与报告的对应字段，再检查 locale 和 awk 实现。不要看到数字变化就宣布内存优化，也不要将主机侧专家配置量当作实测进程峰值。此次案例说明，证据链不仅需要保留日志，还要保留解析条件；一个看起来合理的数字，仍可能是工具制造的偏差。\n\n来源：[club-3090 PR #1930](https:\u002F\u002Fgithub.com\u002Fnoonghunna\u002Fclub-3090\u002Fpull\u002F1930)。","A parser can misreport memory even when the original log is unchanged. Within this window, club-3090 merged PR #1930 to standardize numeric locale handling. It merged at 22:08 UTC on November 3 and documents reproduction and regression checks under a real es_ES.UTF-8 locale. This is a measurement-tool fix, not a new hardware throughput benchmark.\n\n1. Failure mechanism. The source gives host-backed expert amounts of 1.65, 4.56 and 3.81 GB across three cards, totaling 10.02 GB. Under a decimal-comma locale, mawk parsed the dot-separated strings as 1, 4 and 3, then printed their sum as “8,00 GB”. The report also contained mem_total_gib=188,5. Plausible units and magnitudes hid a disagreement with the boot log.\n\n2. Fix. The change forces LC_NUMERIC=C in scripts that perform numeric work and handles LC_ALL, which would otherwise override it. Its previous value is moved to other locale categories before LC_ALL is unset. Fixing only the launcher was insufficient: tools parse their own printed output again, so an intermediate comma can corrupt a later interpretation.\n\n3. Verification boundary. The author reports checks through LANG, LC_NUMERIC and LC_ALL. The functional leg uses real Spanish locale data and mawk, verifies a 10.02 GB sum, and is skipped with a notice if prerequisites are missing. The relevant test set passed 35\u002F35. A broader run was stopped early, so this is not a claim that the entire suite passed. These are upstream self-reported checks, not independently executed tests by AraoAI.\n\nCompare the exact original log fields with the report, then inspect locale settings and the awk implementation. A corrected number is not evidence that the engine reduced memory use. Host-backed expert plan size is also not a measured process peak. Preserving evidence means preserving the parsing conditions as well as the logs: a reasonable-looking number can still be a tooling artifact.\n\nSource: [club-3090 PR #1930](https:\u002F\u002Fgithub.com\u002Fnoonghunna\u002Fclub-3090\u002Fpull\u002F1930).","club-3090 community tooling PR","https:\u002F\u002Fgithub.com\u002Fnoonghunna\u002Fclub-3090\u002Fpull\u002F1930","2026-11-03T23:04:42.479Z"]