No square zone with cursor on Chrome. about openoutpaint HOT 27 CLOSED

The latest version works for me in Incognito, thanks for the quick fix!

from openoutpaint.

can't confirm locally with same chrome on win10 x64 19045.2251 :/

are there any errors listed in the F12 console?

from openoutpaint.

Nope, exept the one stated as "ignore it".

from openoutpaint.

Do the brush tools work?

from openoutpaint.

Well, they work. But no overlay\border thingie.

from openoutpaint.

It seems the overlay canvas is just broken... If you click with the dream tool does the progress bar and such appear?

from openoutpaint.

Yep. Here it is. Generation works too. Tried it out before. I can then accept it and start new gen nearby, just had to find right spot for them to be in line.

from openoutpaint.

yeah, still no luck on reproducing this locally yet :/

from openoutpaint.

Will create a new branch tomorrow to test some of my suspicions. @DanteStormwind could you checkout this new branch, so we can get to the bottom of this?

I'll post a comment here when I get to it.

from openoutpaint.

Shure.

from openoutpaint.

Okay, try checking out the i92 branch version (git checkout i92) and take a screenshot of the console. The screen should also be reddish.

from openoutpaint.

Done. Nothing changed.

from openoutpaint.

Can you go to the network tab, disable caching and try again?

from openoutpaint.

Done. Now its red.

from openoutpaint.

Hm... still no cursor?

from openoutpaint.

Nope. Still nothing.

from openoutpaint.

Hm... That should have printed some debugging info in the console.

Is there some way I can contact you more easily so not to pollute the conversation here? You can DM me on Reddit (u/seijihariki) if you find it okay to schedule a call or something to fix this more effectively. It's also completely fine if you prefer to continue debugging here, it will just take longer, probably.

from openoutpaint.

Fine. I messaged you.

from openoutpaint.

I'm getting a similar issue in both Chrome & Firefox on HEAD (c7a68f3).

Whenever I select the Dream tool, I get a console error. The error message is different in Chrome than it is in Firefox, but seems to be due to the same cause:

Chrome:

FireFox:

from openoutpaint.

I checked out an older version (bd5581f) and everything worked as expected in Chrome. When I went back to HEAD, it continued to work in Chrome. I never refreshed the page while looking at the old version in FireFox and it still doesn't work.

from openoutpaint.

i'm unable to reproduce that error on firefox or chrome (v109 both) on win10x64; could you try refreshing firefox without cache? i know the js hashes should take care of that but hey

from openoutpaint.

I tried clearing the cache and refreshing, also tried opening a private window in FireFox and it doesn't work. My hypothesis is that HEAD can't bootstrap into a valid state but that the older version can. If true, I should be able to checkout the old version, refresh FireFox, see it work, then checkout HEAD and it should continue to work.

...

Confirmed, that fixes it in my FireFox Private window while still being broken in my regular window (which I did not refresh while I had the old version checked out)

from openoutpaint.

My hypothesis is that HEAD can't bootstrap into a valid state but that the older version can.
(which I did not refresh while I had the old version checked out)

i mean i admit regularly to being an idiot so i could very easily be missing the point, but i guarantee openOutpaint doesn't magically update its JS to the newest version in the background if you git pull while it's up and running without refreshing the page ;) i still can't recreate the issue you mentioned however...

including your procedure of verifying reticle exists on v0.0.14 before running git checkout bd5581f..., refreshing page, verifying 0.0.13.2, reticle still exists, git checkout c7a68f3..., no refresh, still v0.0.13.2, still reticle, refresh, 0.0.14 and reticle

from openoutpaint.

Sorry, I think I didn't do a good job of describing what I thought was happening. I think that the JS code in the older version was able to get FF into a coherent state and that the HEAD of main cannot. I believe this state is something that's stored in local, session, or cookie store. I can reliably get either browser back into that incoherent state by opening the latest version in an incognito window.

In other words, it seems to be reproducible by opening up the latest version in incognito mode so that there is no existing state for the app to use.

from openoutpaint.

ahh ok yeah this seems very uhhh different and bad lol, yeah first run in incognito mode is exposing some oversights

from openoutpaint.

alright so abde86d should at least let new installs work - @royvandewater care to check? it's not an elegant fix but should at least prevent the error i believe

from openoutpaint.

will be closing this then as the original post is well over a month out now

from openoutpaint.