gproxy v3.0.4
v3.0.4
Fix v2 upgrades blocked by runtime and historical tables, preserve request logs, and stabilize quota-cycle tracking.
English
Fixed
- v2 SQLite upgrades no longer fail because credential health, cached data, historical aggregates or unknown populated tables exist. Unsupported rate-limit rules and route permissions are skipped and listed in the migration report; supported universal grants remain intact.
- Upstream and downstream request logs migrate with request IDs, timestamps, headers, bodies, response status and multiple upstream attempts. Imports use bounded batches and preserve deleted provider/credential references as disabled historical entries.
- Quota tracking tolerates reset-time drift of up to five minutes against a stable boundary. Rounded zero percentages no longer imply an unused window, and observation ordering and usage-decrease baselines are handled consistently.
Changed
- Historical usage migration preserves retained detail rows and rebuilds v3 aggregates from them. Old rollups, daily credential statistics and quota-cycle history are skipped. The complete v2 database remains in the upgrade backup.
- v2-only log creation/update timestamps and per-attempt latency remain in the backup because v3 has no matching log fields.
- If an earlier failed upgrade left
.gproxy-v2-upgrade-blockedbeside the database, inspect its report and remove that marker before retrying with this version. Keep the database backups and existing master key.
简体中文
修复
- v2 SQLite 升级不再因凭证健康状态、缓存、历史汇总或未知非空表而失败。不支持的限流规则和路由权限会跳过并写入迁移报告，支持的通配权限继续保留。
- 迁移上下游请求日志，保留请求 ID、时间、请求头、正文、响应状态及多次上游重试。日志分批导入；已删除的 Provider 和凭证以禁用的历史条目保留关联。
- 配额周期以固定边界容忍最多五分钟的重置时间偏移；百分比四舍五入为零时不再误判为未使用窗口，并修复观测顺序和用量下降时的基线处理。
变更
- 历史用量仅迁移仍保留的明细，并由明细重建 v3 汇总。旧汇总、凭证每日统计及历史配额周期会跳过，完整 v2 数据库仍保留在升级备份中。
- v2 独有的日志创建/更新时间及单次重试耗时因 v3 无对应字段，仍留在备份中。
- 若此前升级失败，在数据库旁留下了
.gproxy-v2-upgrade-blocked，请查看报告后删除该标记，再使用本版本重试。保留数据库备份和原主密钥。