Closed JaysonPhoenix closed 7 months ago
1047
well i dont quiet understand, does that mention the extension that salesforce-lavis thing belongs to (which is only unprompted i think) wont work when i change the version to the one mentioned in that thread but controlnet zoe will work again? will it check dependencies on startup and change the timm version again so i would have to remove the unprompted extension to avoid it?
anyways, i did what was mentioned in that thread, i used pip install timm==0.6.13 which gave this warning:
Installing collected packages: timm Attempting uninstall: timm Found existing installation: timm 0.4.12 Uninstalling timm-0.4.12: Successfully uninstalled timm-0.4.12 ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. salesforce-lavis 1.0.2 requires timm==0.4.12, but you have timm 0.6.7 which is incompatible. Successfully installed timm-0.6.7
then started automatic1111 which didnt mention updating to another timm version and ran controlnet again but i still got that bug (the same one i think), so that didnt work.
till i get a working solution, would it work to switch the automatic1111 folder again and do the fresh install without ever installing the unprompted extension if its only because of that salesforce thing?
works for me, i deleted venv, unpacked newest auto11 into folder and ran user webui bat file, zoe works , i had same issue before
yeah well as i described i know it works if i do a fresh install and only install controlnet but not when installing my extensions. question is which extension causes the problem and from that other thread i would guess its unprompted (and maybe depthmask2img too idk) and its salesforce dependency which installs the wrong timm if i get that right, so that would temporary help if its only that extension so i could just delete venv on the clean installation with all extensions and if no other extension installs the same thing it should work for now. still id prefer a proper solution so i can use unprompted again and since i dont really understand whats going on under the hood maybe somebody who does should talk to their devs about em upgrading their dependency if possible or whatever each side would have to do to to solve the issue.
well. welcome to a1111. and i think other lib does not really call timm so it is safe to just use another version
i just copied the old installation of before the clean install and removed venv folder and the unprompted extension and the 2 other extensions in question i mentioned that caused errors in clean install to make sure (depthmap2img and ddetailer), because only deleting venv but keeping the extensions would just have the console reinstall the salesforce dependency with its wrong timm lib again and cause the same error. controlnet zoe works now, so it must have been at least one of those 3 extensions causing these incompatibility issues, for at least unprompted i think we can say for sure, so maybe somebody should warn on the controlnet git mainpage temporary not to install that extension till theres a proper solution.
Is there an existing issue for this?
What happened?
yesterday i updated automatic1111 and all extensions at startup and before that everything worked fine and afterwards the depth_zoe preprocessor shows errors (which i dont understand) and is stuck on loading a preview till i reload the ui. the other preprocessors including other depth preprocessors (especially midas, see additional information part) still work fine. because during that update process i had some github connection problems i thought maybe some dependency got corrupted and because my installation is an old one anyway which could profit from some cleaning i decided to make a fresh clean install of the whole stable diffusion including the virtual environment and made a backup moving the folder somewhere else, then i did the clean install and only installed controlnet and its models (without configs since they are now part of the extension) and tested the preprocessors and everything worked fine again, then i did a clean install of all extensions i had and then tested controlnet again and i got the same error. so i would guess its some kind of incompatibility that was introduced during the update i made yesterday (since i didnt install any new extensions or made any changes, only updated while restarting the ui, including installing/updating dependencies).
Steps to reproduce the problem
check pixel perfect and allow preview load picture select depth_zoe preprocessor click generate preview error and no depthmap
What should have happened?
generate depthmap instead of error ^^
Commit where the problem happens
webui:
version: v1.3.0 • python: 3.10.6 • torch: 2.0.1+cu118 • xformers: N/A • gradio: 3.31.0 • checkpoint: 2bd89c4fad
controlnet: v1.1.202 (main)
What browsers do you use to access the UI ?
No response
Command Line Arguments
List of enabled extensions
active extensions:
a1111-sd-webui-lycoris a1111-sd-webui-tagcomplete Auto-Photoshop-StableDiffusion-Plugin canvas-zoom Config-Presets embedding-inspector Hypernetwork-MonkeyPatch-Extension multidiffusion-upscaler-for-automatic1111 openOutpaint-webUI-extension openpose-editor PBRemTools prompt-fusion-extension sd-dynamic-prompts sd-dynamic-thresholding sd-model-preview-xd sd-webui-3d-open-pose-editor sd-webui-additional-networks sd-webui-aspect-ratio-helper sd-webui-controlnet sd-webui-cutoff sd-webui-infinite-image-browsing sd-webui-llul sd-webui-neutral-prompt sd-webui-photopea-embed sd-webui-prompt-all-in-one sd-webui-regional-prompter stable-diffusion-webui-anti-burn Stable-Diffusion-Webui-Civitai-Helper stable-diffusion-webui-composable-lora stable-diffusion-webui-state stable-diffusion-webui-tokenizer stable-diffusion-webui-two-shot StylePile ultimate-upscale-for-automatic1111 unprompted weight_gradient
disabled extensions:
sd-web-ui-quickcss sd-webui-ar sd-webui-model-converter stable-diffusion-webui-aesthetic-gradients stable-diffusion-webui-dataset-tag-editor stable-diffusion-webui-embedding-editor stable-diffusion-webui-images-browser stable-diffusion-webui-model-toolkit
Console logs
Additional information
i removed 2 extensions because they were throwing errors after clean stable diffusion installation seemingly because of some failing mm-something dependency installation on every restart even when the extensions are disabled (but they were working before the clean installation). i'll still mention them because they seem related, especially the depth2img one using midas and i remember reading words on their gits like beit and timm which are mentioned in the controlnet error. i also remember some extension cloned something with midas from controlnet during its installation and i would guess it was the depth2img one but i cant tell for sure, too many extensions, maybe its unrelated but maybe it helps. the 2 extensions were ddetailer and depthmap2mask