ljleb
ljleb
@aiton-sd Sorry to bother you. As you wrote some code recently related to external code access, I'd love to hear your opinion on this issue. How do you think external...
> Btw, my 2 cents is that having to use the arg method (figuring out where in the pile of all settings, ordered but unlabeled, the changes are needed) is...
I don't think we want to start counting with the prop names 😅 but yeah I think a list property just like we did for the rest api would work...
I'm working on a PR for this, I'll open it when I get the controlnet routes in the web api to work with it as a proof of concept.
This and #940 are caused by our module paths not being unique. We should prefix the names with `lib_controlnet_` or something like that.
Yes, by manipulating sys.path I presume. I am not sure if this could break something else unexpectedly again though,and if it can actually work. Going with the unique module names...
It's a bit unfortunate. It feels like every time I commit something, something else unexpectedly breaks. In this case the underlying issue is not even something I wrote code for....
Yes sys.path looks for imports in the order the paths are listed. i.e. we could try reordering. Again, I am not convinced this is the way to go and if...
I don't know, is it related to the values in sys.path? Put a breakpoint or print its value when loading controlnet.py. Are there extensions that import the annotator module? I...
Look at the body of the issue here. It actually has the same rules as outside scripts. i.e. we cannot import xyz_grid_support.