Eugene Brodsky

@cyperium : `E:\InvokeAI\onfigure` looks incredibly odd. Did you use the exact installation steps posted by @delizin above? Somehow your path is mangled in a way I haven't see before. Edit:...

This is a bit odd: ``` Q:\InvokeAI\.venv\lib\site-packages\diffusers\pipelines\dance_diffusion\__init__.py:2 │ │ in │ │ │ │ 1 # flake8: noqa │ │ ❱ 2 from .pipeline_dance_diffusion import DanceDiffusionPipeline │ │ 3 ```...

Indeed. It's just the path it took to get to the problem that looked odd to me. Thanks for clarifying the `diffusers` behaviour. @Coreusa it's unclear what might be causing...

Great suggestion, thank you. we can add `black` to the dev toolchain and have it run in the workflows at least in the `--check-only` mode, but i'm afraid allowing CI...

+1. need to be able to "UNEXPOSE" default nginx ports 80 and 443.

I added a commit that re-enables previously skipped test suites, so that we know what's actually failing and needs fixing

> Uhh I'm a bit confused, I had fixed everything so that all tests passed except the textual inversion suite. Why are these other changes needed? Because I had skipped...

> By creating the mock invocation services in their own module, the union is constructed before the test node classes are loaded into memory. During tests, the test node types...

Hey @briancaffey - thank you for the contribution. We're actually refactoring the docker setup quite heavily in https://github.com/invoke-ai/InvokeAI/pull/3587. Would you mind giving that PR a look? Right now it's still...

Should this be rolled into #3547 , or merged separately following that?