Skip to content
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

Lightning compatibility fix #281

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

alihassanijr
Copy link

Hello,

I'm unsure if this repository is still maintained, but I had to resolve this on my own so I figured I'd open a PR as well in case it still is maintained.

Due to a change in lightning's tree structure there will be an import failure if someone has to upgrade lighting, which was the case for me.
This commit just changes that one import line and attempt to import assuming it's the new version, and if it fails it'll fall back to trying to import the old one.

Newer lighting versions move `rank_zero_only` from the distributed
subpackage back to utilities. This commit adds a try-except to catch
that import error, and retry with the alternative.
@soulteary
Copy link

soulteary commented Jan 17, 2024

@rromb , @hardmaru , could this can merge?

If this change wants to be merged, is there anything else that needs to be done?

If it completes the merge, the downstream repository can normally use the complete PyTorch. 2.x software and obtain higher performance. For example: Stable Diffusion WebUI, etc.

refs: AUTOMATIC1111/stable-diffusion-webui#14665

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