loft-sh / devpod

Codespaces but open-source, client-only and unopinionated: Works with any IDE and lets you use any cloud, kubernetes or just localhost docker.
https://devpod.sh
Mozilla Public License 2.0
8.43k stars 307 forks source link

On initial UI AppImage startup: { "name": "ContextError" } #1035

Closed schlegel11 closed 2 months ago

schlegel11 commented 2 months ago

What happened? On initial DevPod app image startup so after:

The UI opens with error pane (see screenshot) { "name": "ContextError" }. devpod-bug

Further the DevPod.log contents:

[2024-04-28][17:15:19][INFO][devpod_desktop] Setup application
[2024-04-28][17:15:19][WARN][tauri_plugin_store] Failed to load store "/home/user/.local/share/sh.loft.devpod/.providers.json" from disk: File or directory not found (os error 2). Falling back to default values.
[2024-04-28][17:15:20][INFO][devpod_desktop] Setup done
[2024-04-28][17:15:20][INFO][devpod_desktop] Run
[2024-04-28][17:15:20][INFO][devpod_desktop::server] Listening on 127.0.0.1:25842
[2024-04-28][17:15:21][WARN][tauri_plugin_store] Failed to load store ".settings.json" from disk: File or directory not found (os error 2). Falling back to default values.
[2024-04-28][17:15:21][WARN][tauri_plugin_store] Failed to load store ".providers.json" from disk: File or directory not found (os error 2). Falling back to default values.

It just happens on initial startup. Afterwards there is no such behaviour and everything works fine.

What did you expect to happen instead?

No error screen on initial startup. Just normal overview/main pane opens.

How can we reproduce the bug? (as minimally and precisely as possible)

Start the app image for the first time like:

Local Environment:

pascalbreuninger commented 2 months ago

Hey @schlegel11, thanks for opening the issue, we'll look into it

schlegel11 commented 2 months ago

Maybe there is no need to investigate the issue :wink: It seems to be fixed with version 0.5.6. At least for me.

pascalbreuninger commented 2 months ago

perfect! I'll go ahead and close this issue. If you experience this error again let us know