fix: vace specific output ports when topology is not specified#777
fix: vace specific output ports when topology is not specified#777
Conversation
Signed-off-by: gioelecerati <[email protected]>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🚀 fal.ai Preview Deployment
Livepeer Runner
TestingConnect to this preview deployment by running this on your branch: Livepeer mode: 🧪 E2E tests will run automatically against this deployment. |
❌ E2E Tests failed
Test ArtifactsCheck the workflow run for screenshots, traces, and failure details. |
When importing a legacy workflow without the graph topology that includes vace specific output ports (example: https://app.daydream.live/workflows/hthillman/pixel-art-preserved-background includes a yolo mask node with vace outputs), we generate the topology correctly with this fix