fix: 仅对储存历史CSV使用GBK

This commit is contained in:
2026-08-07 16:37:20 +08:00
parent 8a3c273a04
commit 8e96b3a24b
5 changed files with 36 additions and 19 deletions
+1 -1
View File
@@ -48,7 +48,7 @@ After the database succeeds, the same eleven result columns are uploaded as GBK
The filename time comes from normalized `metric_time`, never the server clock. If the database already contains the target time but its history CSV is missing or empty, the script exports that time from the database and repairs the history file without reprocessing source data.
All generated CSV files use GBK without a UTF-8 BOM, including the seven converted source files, the merged summary, and the uploaded history file. Source non-breaking spaces (`U+00A0`) are normalized to ordinary spaces because GBK cannot encode them; other unsupported characters still fail the run instead of being silently replaced. `manifest.json` remains UTF-8 JSON.
Only the final history CSV uploaded to Metrix Storage uses GBK without a UTF-8 BOM. Source non-breaking spaces (`U+00A0`) are normalized to ordinary spaces in this history file because GBK cannot encode them; other unsupported characters still fail visibly. The seven local converted CSV files and local merged summary remain UTF-8 with BOM, and `manifest.json` remains UTF-8 JSON.
CGI is generated with fixed rules: