Stuck GUI

[unclemusclez]

I've uninstalled, reinstalled, redid the settings, etc. I don't know why this is stuck. This is happened over multiple versions. I don't know if it's my settings, but this seems to be particular to using Twinny within my WSL instance. not sure if it is related.

I'd diagnose this further if you give me any feedback.

Uncaught RangeError: Maximum call stack size exceeded
    at handleToggleProviderSelection (sidebar.js:110816:7)
    at handleToggleEmbeddingOptions (sidebar.js:110827:33)
    at handleToggleProviderSelection (sidebar.js:110816:40)
    at handleToggleEmbeddingOptions (sidebar.js:110827:33)
    at handleToggleProviderSelection (sidebar.js:110816:40)
    at handleToggleEmbeddingOptions (sidebar.js:110827:33)
    at handleToggleProviderSelection (sidebar.js:110816:40)
    at handleToggleEmbeddingOptions (sidebar.js:110827:33)
    at handleToggleProviderSelection (sidebar.js:110816:40)
    at handleToggleEmbeddingOptions (sidebar.js:110827:33)

update:

after deleting my WSL .vscode folder and then uninstalling my local Twinny extension, i was able to release the GUI.

i don't think this is expected behavior. I did this recently as well, wiping all of my across all instances, in order to get Twinny to function. I believe this is an issue specific to Twinny settings and workspace/user/remote settings.

...and its gone.. i reinstalled the extension to the local instance first, upon reinstalling the plugin to the wsl instance, the GUI locked up again.

i deleted ALL of my settings from both environments. the .vscode and .vscode_server folders.

also ssl settings seemed to not work correctly, but over http with the assigned port seems to work. twinny doesnt seem to play well with reverse proxy settings and ports. i dont think a port should be required for open-webui in the case the port is forwarded to a domain name.

[rjmacarthy]

Hey thanks for the report. It seems like some kind of rendering loop with react, any concrete steps to replicate, it doesn't happen for me?

[unclemusclez]

@rjmacarthy the bug seems to present itself within ubuntu wsl2. my local instance does not have this issue. i removed the local instance, and the issue persisted, even with completely wiped and reset settings and installation.

I dont think it's every version, i've noticed that this bug goes away and then comes back. it's been hard to pin point everything because ive been trying to also set up twinny with openwebui, and there have been multiple changes in the past couple of weeks between that and the version of ollama i am running. plus, i just migrated my instance from my local machine to a dedicated server.

i'd love to help debug this futher and contribute but i use twinny to do all of my coding 😥. it's a vicious cycle

[rjmacarthy]

There have been multiple issues with WSL but I don't have windows installed to be able to even attempt to fix it.