is inpaint broken? and this plugin still supported?

[danilw]

This is result of inpaint in Krita, on "this" latest(just launched and updated) plugin version.

On server image is correct:

This happening only on image transfer, because server image is okey. Only in inpaint, img2img is fine. Happening when backend on "remote" and "localhost", I think this is not about internet speed.

Is this plugin still supported? Or you just switch on https://github.com/Interpause/auto-sd-paint-ext?

[Interpause]

I will no longer be maintaining this version of the plugin, so I will move the issue over later.

But this is a weird bug. What was your selection region & inpaint layer?

[danilw]

But this is a weird bug. What was your selection region & inpaint layer?

I was making https://github.com/Interpause/auto-sd-krita/issues/32 and was not sure is it "my encryption bug" or this plugin and maybe it was updated, had no internet for few days, and was sitting on old version. Today checked last version - it still there.

Selection look like this: (this is not from first post selection, but result same)

img size: 524x327 -> 512x320, aspect ratio: 1.60 -> 1.60, -0.15% change

Only in inpaint, when on "localhost" it has - "broken cuts as lines", but when from Colab - cuts look like dots, noise with transparent dots everywhere.

I think if it "internet problem" or Async broke somehow - then it should happen in img2img also, but img2img always fine, I tested many times today.

(I used this plugin before Async change - it was working fine, not this "cuts-bug", I used inpaint many times lasst week, so I would notice for sure)

[Interpause]

Under defaults.py in krita_server, there is a option THREADED. Set it to false to disable async. You also already tried with your encryption off right?

Send me the link to your fork, I'll see if I can reproduce the issue & figure out what is going on.

[danilw]

You also already tried with your encryption off right?

yes - I tried with and without encryption (on clean clone of this your repository, because obviously I thought it my bug).

I have not updated Krita for 2 weeks so it same version for all this time.

Maybe it somehow related to Linux version of Python, because server I running on localhost is on Linux, and same with Colab - there Linux.

Il post more detailed report today.

[danilw]

Under defaults.py in krita_server, there is a option THREADED

it was in krita-client, and set it to False does not change anything

but since you not support this plugin anymore - il just close this issue

[Interpause]

I see, its fine. Do let me know if you encounter the issue in the new version because I have yet to encounter it.