fix: videoRatio aspect ratio parsed as resolution causing scale=9:1920 #1364

Merged
xiaoxia merged 2 commits from fix/video-ratio-resolution-parsing into develop 2026-08-14 00:56:54 +08:00
Owner

Root Cause

videoRatio stores aspect ratio format (e.g. "9:16") but useGenerateVideo.ts parsed it as resolution with .split("x"). parseInt("9:16", 10) returns 9, causing FFmpeg scale=9:1920 to fail.

Fixes

  • Frontend: Parse aspect ratio (colon format) and compute actual pixel dimensions
  • Backend worker: Guard output_width < 100, fallback to default
  • Backend render_adapter: Guard width/height < 100 in _parse_resolution
  • API schema: Add ge=100 validation on ConfirmGenerationRequest
## Root Cause videoRatio stores aspect ratio format (e.g. "9:16") but useGenerateVideo.ts parsed it as resolution with .split("x"). parseInt("9:16", 10) returns 9, causing FFmpeg scale=9:1920 to fail. ## Fixes - **Frontend**: Parse aspect ratio (colon format) and compute actual pixel dimensions - **Backend worker**: Guard output_width < 100, fallback to default - **Backend render_adapter**: Guard width/height < 100 in _parse_resolution - **API schema**: Add ge=100 validation on ConfirmGenerationRequest
xiaoxia added 1 commit 2026-08-14 00:16:49 +08:00
fix: videoRatio aspect ratio parsed as resolution causing scale=9:1920
CI/CD Pipeline / Build Staging API Image (pull_request) Has been skipped
CI/CD Pipeline / Build Staging Web Image (pull_request) Has been skipped
CI/CD Pipeline / Build Staging Worker Image (pull_request) Has been skipped
CI/CD Pipeline / Deploy Staging (Watchtower auto-deploy) (pull_request) Has been skipped
CI/CD Pipeline / Staging E2E Tests (pull_request) Has been skipped
CI/CD Pipeline / ACR Image Cleanup (pull_request) Has been skipped
CI/CD Pipeline / Staging API Integration Tests (pull_request) Has been skipped
CI/CD Pipeline / Check if frontend-only change (pull_request) Successful in 27s
CI/CD Pipeline / Frontend Unit Tests (pull_request) Successful in 45s
CI/CD Pipeline / Frontend Lint (pull_request) Successful in 1m12s
PR Automation / Auto Merge on CI Green + Approved (pull_request) Successful in 1m54s
CI/CD Pipeline / PR Build Web Image (pull_request) Successful in 1m52s
CI/CD Pipeline / PR Build Worker Image (pull_request) Successful in 1m27s
Preview Deploy / Deploy Preview Environment (pull_request) Successful in 3m11s
PR Automation / Auto Approve on CI Green (pull_request) Successful in 3m52s
AI Code Review / AI Code Review (pull_request) Failing after 3m54s
CI/CD Pipeline / Validate - Migration (alembic) (pull_request) Successful in 11m8s
CI/CD Pipeline / Validate - Type Check (mypy) (pull_request) Successful in 12m55s
CI/CD Pipeline / Validate - Code Quality (pull_request) Has been cancelled
CI/CD Pipeline / Unit Tests (pull_request) Has been cancelled
CI/CD Pipeline / Integration Tests (pull_request) Has been cancelled
CI/CD Pipeline / PR Build API Image (pull_request) Has been cancelled
CI/CD Pipeline / Build Production API Image (pull_request) Has been cancelled
CI/CD Pipeline / Build Production Web Image (pull_request) Has been cancelled
CI/CD Pipeline / Build Production Worker Image (pull_request) Has been cancelled
CI/CD Pipeline / Deploy Production (pull_request) Has been cancelled
CI/CD Pipeline / Production Browser E2E (pull_request) Has been cancelled
CI/CD Pipeline / Canary Release to Production (pull_request) Has been cancelled
CI/CD Pipeline / CI Gate (pull_request) Has been cancelled
aacf83dc05
Root cause: videoRatio stores aspect ratio format (e.g. "9:16") but
useGenerateVideo.ts parsed it as resolution with .split("x"), causing
parseInt("9:16") to return 9 instead of 1080.

Fixes:
- Frontend: parse aspect ratio (colon format) and compute pixel dims
- Backend worker: guard output_width < 100, fallback to default
- Backend render_adapter: guard width/height < 100 in _parse_resolution
- API schema: add ge=100 validation on ConfirmGenerationRequest

🚀 预览环境已部署

项目 详情
PR号 #1364
预览链接 https://pr-1364.preview.xiaoxiajianji.com
API环境 staging

💡 预览环境使用 staging API 数据,请勿在预览环境中操作重要数据。

🔄 每次提交新代码后预览环境会自动更新。

🗑️ PR 关闭或合并后,预览环境会自动清理。

🚀 **预览环境已部署** | 项目 | 详情 | |------|------| | PR号 | #1364 | | 预览链接 | [https://pr-1364.preview.xiaoxiajianji.com](https://pr-1364.preview.xiaoxiajianji.com) | | API环境 | staging | > 💡 预览环境使用 staging API 数据,请勿在预览环境中操作重要数据。 > > 🔄 每次提交新代码后预览环境会自动更新。 > > 🗑️ PR 关闭或合并后,预览环境会自动清理。
Collaborator

【阻塞级判定】

  • 是否存在阻塞级问题:是
  • 阻塞级问题数量:1 个

📊 审查概览

  • 整体评价:需修改
  • 建议级问题数量:1 个

🔴 阻塞级问题(必须修复)

  1. [apps/web/src/pages/generate/hooks/useGenerateVideo.ts: 64] 极端宽高比导致分辨率计算为0
    • 问题类型:逻辑bug / 边界条件遗漏
    • 问题描述:在计算偶数短边时,使用了 baseShort - (baseShort % 2)。当宽高比差异极大(如 2000:1)时,baseShort 计算结果可能为 1(例如 Math.round(1920 * 1 / 2000) = 1)。此时 1 - (1 % 2) 结果为 0。导致发送给后端的 output_widthoutput_height 为 0,触发后端 Pydantic 验证错误(ge=100),导致生成任务失败。
    • 修改建议:确保计算出的短边至少为 2(或符合后端最小值 100)。建议修改为:const evenShort = Math.max(2, baseShort - (baseShort % 2))

💡 改进建议(不阻塞合并)

  1. [apps/web/src/pages/generate/hooks/useGenerateVideo.ts: 74] 前端解析未对齐后端最小值限制
    • 具体内容:后端 Schema 已添加 ge=100 的限制,但在处理 "1080x1920" 格式时,前端仅使用 parseInt(..., 10) || 1080。如果用户输入或配置传入 "50x1920",前端会正常解析并发送 50,随后被后端拦截(422 Error)。建议在前端解析时也增加最小值校验(如 Math.max(100, parseInt(...))),提升用户体验,避免无效请求。

良好实践

  1. 后端防御性编程:在 generation.pyrender_adapter.py 中增加了 < 100 的校验和日志记录,有效防止了前端误传宽高比字符串(如 "9:16" 被解析为 9)导致的渲染崩溃。
  2. Pydantic 约束增强:在 generation_task.py 中为 output_width/height 添加了 ge=100 约束,从数据模型层保证了数据的合法性。

格式检查通过 | 逻辑审查需修改 | 性能良好


🤖 由 AI 代码审查机器人自动生成 | 2026-08-13 16:20:43 | 模型:

### 【阻塞级判定】 - 是否存在阻塞级问题:是 - 阻塞级问题数量:1 个 ### 📊 审查概览 - 整体评价:需修改 - 建议级问题数量:1 个 ### 🔴 阻塞级问题(必须修复) 1. **[apps/web/src/pages/generate/hooks/useGenerateVideo.ts: 64] 极端宽高比导致分辨率计算为0** - 问题类型:逻辑bug / 边界条件遗漏 - 问题描述:在计算偶数短边时,使用了 `baseShort - (baseShort % 2)`。当宽高比差异极大(如 2000:1)时,`baseShort` 计算结果可能为 1(例如 `Math.round(1920 * 1 / 2000) = 1`)。此时 `1 - (1 % 2)` 结果为 `0`。导致发送给后端的 `output_width` 或 `output_height` 为 0,触发后端 Pydantic 验证错误(`ge=100`),导致生成任务失败。 - 修改建议:确保计算出的短边至少为 2(或符合后端最小值 100)。建议修改为:`const evenShort = Math.max(2, baseShort - (baseShort % 2))`。 ### 💡 改进建议(不阻塞合并) 1. **[apps/web/src/pages/generate/hooks/useGenerateVideo.ts: 74] 前端解析未对齐后端最小值限制** - 具体内容:后端 Schema 已添加 `ge=100` 的限制,但在处理 "1080x1920" 格式时,前端仅使用 `parseInt(..., 10) || 1080`。如果用户输入或配置传入 "50x1920",前端会正常解析并发送 50,随后被后端拦截(422 Error)。建议在前端解析时也增加最小值校验(如 `Math.max(100, parseInt(...))`),提升用户体验,避免无效请求。 ### ✅ 良好实践 1. **后端防御性编程**:在 `generation.py` 和 `render_adapter.py` 中增加了 `< 100` 的校验和日志记录,有效防止了前端误传宽高比字符串(如 "9:16" 被解析为 9)导致的渲染崩溃。 2. **Pydantic 约束增强**:在 `generation_task.py` 中为 `output_width/height` 添加了 `ge=100` 约束,从数据模型层保证了数据的合法性。 --- ✅ 格式检查通过 | ❌ 逻辑审查需修改 | ✅ 性能良好 --- <sub>🤖 由 AI 代码审查机器人自动生成 | 2026-08-13 16:20:43 | 模型: </sub> <!-- AI_CODE_REVIEW_AUTO_COMMENT -->
auto-approve-bot added 1 commit 2026-08-14 00:30:38 +08:00
style: auto-format with black + isort + prettier [skip ci-format-check]
CI/CD Pipeline / Build Staging API Image (pull_request) Has been skipped
CI/CD Pipeline / Build Staging Web Image (pull_request) Has been skipped
CI/CD Pipeline / Build Staging Worker Image (pull_request) Has been skipped
CI/CD Pipeline / Deploy Staging (Watchtower auto-deploy) (pull_request) Has been skipped
CI/CD Pipeline / Staging E2E Tests (pull_request) Has been skipped
CI/CD Pipeline / Staging API Integration Tests (pull_request) Has been skipped
CI/CD Pipeline / Check if frontend-only change (pull_request) Successful in 32s
CI/CD Pipeline / Frontend Unit Tests (pull_request) Successful in 42s
CI/CD Pipeline / Frontend Lint (pull_request) Successful in 1m1s
PR Automation / Auto Merge on CI Green + Approved (pull_request) Successful in 1m52s
Preview Deploy / Deploy Preview Environment (pull_request) Successful in 2m9s
CI/CD Pipeline / PR Build Web Image (pull_request) Successful in 1m45s
CI/CD Pipeline / PR Build Worker Image (pull_request) Successful in 1m28s
PR Automation / Auto Approve on CI Green (pull_request) Successful in 3m32s
CI/CD Pipeline / Validate - Migration (alembic) (pull_request) Successful in 5m56s
CI/CD Pipeline / Validate - Type Check (mypy) (pull_request) Successful in 6m59s
AI Code Review / AI Code Review (pull_request) Successful in 7m11s
CI/CD Pipeline / PR Build API Image (pull_request) Successful in 9m48s
CI/CD Pipeline / ACR Image Cleanup (pull_request) Failing after 14m44s
CI/CD Pipeline / Validate - Code Quality (pull_request) Successful in 16m15s
CI/CD Pipeline / Unit Tests (pull_request) Successful in 19m42s
CI/CD Pipeline / Build Production API Image (pull_request) Has been skipped
CI/CD Pipeline / Build Production Web Image (pull_request) Has been skipped
CI/CD Pipeline / Build Production Worker Image (pull_request) Has been skipped
CI/CD Pipeline / Deploy Production (pull_request) Has been skipped
CI/CD Pipeline / Canary Release to Production (pull_request) Has been skipped
CI/CD Pipeline / Production Browser E2E (pull_request) Has been skipped
CI/CD Pipeline / Integration Tests (pull_request) Successful in 8m36s
CI/CD Pipeline / CI Gate (pull_request) Successful in 7s
ACR Cleanup / ACR Image Cleanup (pull_request_target) Successful in 40s
Preview Cleanup / Cleanup Preview Environment (pull_request) Successful in 1m33s
330710d008
auto-approve-bot approved these changes 2026-08-14 00:50:30 +08:00
auto-approve-bot left a comment
Collaborator

CI全绿,自动审批通过。

CI全绿,自动审批通过。
auto-approve-bot approved these changes 2026-08-14 00:50:30 +08:00
auto-approve-bot left a comment
Collaborator

CI全绿,自动审批通过。

CI全绿,自动审批通过。
xiaoxia merged commit 8e4a8a8184 into develop 2026-08-14 00:56:54 +08:00

🗑️ 预览环境已清理

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

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

🗑️ **预览环境已清理** PR #1364 已关闭或合并,对应的预览环境已被清理。 > 如有需要,可以重新打开 PR 来重新生成预览环境。
Sign in to join this conversation.