Skip to content

another fix for FlowMatchLCMScheduler forgotten import #11330

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 15, 2025

Conversation

asomoza
Copy link
Member

@asomoza asomoza commented Apr 15, 2025

I had to switch systems to do the fix-copies and somehow this was not included to the original PR.

@yiyixuxu

@asomoza asomoza changed the title fix for FlowMatchLCMScheduler with #11318 another fix for FlowMatchLCMScheduler with #11318 Apr 15, 2025
@asomoza
Copy link
Member Author

asomoza commented Apr 15, 2025

I noticed that we don't have tests for any of the newer schedulers, maybe we can open them to the community? If not, I can add it to my TODOs since I think this is important, my mistake should've a failed test and I didn't manually check this because I was confident that there were some tests for the imports.

cc: @sayakpaul

@HuggingFaceDocBuilderDev

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

@asomoza asomoza changed the title another fix for FlowMatchLCMScheduler with #11318 another fix for FlowMatchLCMScheduler forgotten import Apr 15, 2025
@yiyixuxu yiyixuxu merged commit d3b2699 into main Apr 15, 2025
15 checks passed
@yiyixuxu yiyixuxu deleted the another-fix-for-flowmatchlcmscheduler branch April 15, 2025 23:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants