xiaoxia/xiaoxia-saas
1
0
Fork 0
Code Issues 16 Pull Requests 13 Actions 34.2k Packages Projects Releases 7 Wiki Activity

fix(worker): 修复像素扰动color_balance滤镜名错误导致模板编辑器FFmpeg exit=8 #1880

Merged
xiaoxia merged 1 commits from fix/colorbalance-filter-name-0913 into develop 2026-09-14 00:07:36 +08:00
Conversation 1 Commits 1 Files Changed 1
+2 -2
xiaoxia commented 2026-09-13 23:36:16 +08:00
Owner
Copy Link
Copy Source

根因

像素扰动功能(提交bb98620)在ffmpeg滤镜链中写了color_balance=rs=...，但FFmpeg的实际滤镜名是colorbalance（一个单词，无下划线）。当变体渲染随机选到color_balance扰动时，ffmpeg报"No such filter: 'color_balance'"，退出码8。

表现：模板编辑器批量渲染卡在56%进度，error_message被截断只显示ffmpeg banner，看不到真正错误。

修改

  • unified_render_service.py：ffmpeg滤镜名从 color_balance= 改为 colorbalance=
  • 内部config key（variant_plan_selector中的"color_balance"）保持不变，避免兼容问题

验证

  • 本地ffmpeg -filters确认滤镜名为colorbalance（T.C=支持时间轴+命令行参数）
  • PR#1879部署后拿到了完整stderr，定位到具体报错行
  • 修复后重试任务应该成功渲染
## 根因 像素扰动功能(提交bb98620)在ffmpeg滤镜链中写了`color_balance=rs=...`，但FFmpeg的实际滤镜名是`colorbalance`（一个单词，无下划线）。当变体渲染随机选到color_balance扰动时，ffmpeg报"No such filter: 'color_balance'"，退出码8。 表现：模板编辑器批量渲染卡在56%进度，error_message被截断只显示ffmpeg banner，看不到真正错误。 ## 修改 - `unified_render_service.py`：ffmpeg滤镜名从 `color_balance=` 改为 `colorbalance=` - 内部config key（variant_plan_selector中的`"color_balance"`）保持不变，避免兼容问题 ## 验证 - 本地ffmpeg -filters确认滤镜名为colorbalance（T.C=支持时间轴+命令行参数） - PR#1879部署后拿到了完整stderr，定位到具体报错行 - 修复后重试任务应该成功渲染
xiaoxia added 1 commit 2026-09-13 23:36:17 +08:00
fix(worker): 修复像素扰动color_balance滤镜名错误导致ffmpeg exit=8
CI/CD Pipeline / Check if frontend-only change (pull_request) Successful in 5s
Details
CI/CD Pipeline / PR Build Worker Image (pull_request) Successful in 21s
Details
CI/CD Pipeline / PR Build API Image (pull_request) Successful in 32s
Details
CI/CD Pipeline / Dedup Check - skip PR tests when covered by push pipeline (pull_request) Failing after 13m45s
Details
CI/CD Pipeline / Integration Tests (pull_request) Successful in 6m21s
Details
CI/CD Pipeline / Unit Tests (pull_request) Successful in 6m49s
Details
CI/CD Pipeline / Validate - Style (pull_request) Successful in 7m5s
Details
CI/CD Pipeline / Validate - Python (mypy + alembic) (pull_request) Successful in 8m39s
Details
CI/CD Pipeline / Validate - Security (pull_request) Successful in 15m14s
Details
CI/CD Pipeline / CI Gate (pull_request) Successful in 1s
Details
CI/CD Pipeline / Production Browser E2E (pull_request) Has been skipped
Details
ACR Cleanup / ACR Image Cleanup (pull_request_target) Successful in 6s
Details
Preview Cleanup / Cleanup Preview Environment (pull_request) Successful in 1m4s
Details
CI/CD Pipeline / Deploy Production (pull_request) Failing after 63h18m24s
Details
CI/CD Pipeline / Staging E2E Tests (pull_request) Failing after 63h47m15s
Details
CI/CD Pipeline / Retag skipped Staging Web Image (pull_request) Failing after 63h47m17s
Details
CI/CD Pipeline / Build Staging Web Image (pull_request) Failing after 63h47m19s
Details
CI/CD Pipeline / Build Production Worker Image (pull_request) Failing after 63h18m0s
Details
CI/CD Pipeline / PR Build Web Image (pull_request) Failing after 63h46m55s
Details
CI/CD Pipeline / Build Production API Image (pull_request) Failing after 63h18m0s
Details
CI/CD Pipeline / Deploy Staging (Watchtower auto-deploy) (pull_request) Failing after 63h46m51s
Details
CI/CD Pipeline / Retag skipped Staging Worker Image (pull_request) Failing after 63h46m51s
Details
CI/CD Pipeline / Retag skipped Staging API Image (pull_request) Failing after 63h46m53s
Details
CI/CD Pipeline / Build Staging Worker Image (pull_request) Failing after 63h46m54s
Details
CI/CD Pipeline / Build Staging API Image (pull_request) Failing after 63h46m54s
Details
CI/CD Pipeline / Check push changed paths (pull_request) Failing after 63h47m4s
Details
CI/CD Pipeline / ACR Image Cleanup (pull_request) Failing after 63h46m49s
Details
CI/CD Pipeline / Staging API Integration Tests (pull_request) Failing after 63h46m49s
Details
CI/CD Pipeline / Canary Release to Production (pull_request) Failing after 63h17m59s
Details
CI/CD Pipeline / Build Production Web Image (pull_request) Failing after 63h18m0s
Details
CI/CD Pipeline / Frontend Unit Tests (pull_request) Failing after 63h33m14s
Details
CI/CD Pipeline / Frontend Lint (pull_request) Failing after 63h33m15s
Details
b9acf8c86f 
根因：像素扰动功能(bb98620)在ffmpeg滤镜链中使用了color_balance滤镜名，
但ffmpeg的实际滤镜名是colorbalance（无下划线），导致滤镜解析失败，
报错'No such filter: color_balance'，ffmpeg退出码8。

影响：任何启用了像素扰动的变体渲染（默认批量变体会随机启用）都会失败，
表现为进度卡在56%，error_message只显示ffmpeg版本banner。

修复：将ffmpeg滤镜名从color_balance=改为colorbalance=。
内部config key保持color_balance不变（避免兼容问题）。
xiaoxia merged commit 5b931438e0 into develop 2026-09-14 00:07:36 +08:00
gitea-actions bot commented 2026-09-14 00:08:39 +08:00
Copy Link
Copy Source

🗑️ 预览环境已清理

PR #1880 已关闭或合并，对应的预览环境已被清理。

如有需要，可以重新打开 PR 来重新生成预览环境。

🗑️ **预览环境已清理** PR #1880 已关闭或合并，对应的预览环境已被清理。 > 如有需要，可以重新打开 PR 来重新生成预览环境。
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
architecture
架构设计
 backend
后端相关
 blocked
阻塞中
 bug
Bug修复
 ci-bug
CI本身的bug
 ci-optimization
CI优化类任务
 ci-pipeline
CI流水线/workflow相关
 cleanup
代码清理
 devops
运维/部署/CI
 documentation
文档相关
 feature
新功能
 frontend
前端相关
 P0
阻塞性，必须立即处理
 P1
高优先级
 P2
中优先级
 P3
低优先级/后考虑
 question
需要讨论确认
 ready
PR CI通过，可合并
 refactor
代码重构
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
auto-approve-bot frontend-dev xiaoxia
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: xiaoxia/xiaoxia-saas#1880
Delete Branch "fix/colorbalance-filter-name-0913"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?