Skip to content

docs: record the dialog and the read-only install runs - #2

Merged
jeffreyaven merged 1 commit into
mainfrom
installed-state-notes
Nov 20, 2026
Merged

jeffreyaven merged 1 commit into
mainfrom
installed-state-notes

Conversation

@jeffreyaven

Copy link
Copy Markdown
Member

Documentation only. It records two runs made after #1 was merged, and two questions that came out of them.

What was run

  • The check for a missing WebView2 runtime, on the optimised build from CI. With the loader pointed at an empty folder, which is what a machine with no runtime looks like to it, the app showed its own dialog: "StackQL Workbench requires the Microsoft Edge WebView2 Runtime", and under it one sentence with a link to Microsoft's page. There was no terminal: the process had no console host, where a debug build has one. It exited with code 1 when the dialog was closed. A click on the link brought Microsoft's page up in the browser.
  • An install an ordinary account cannot write to. The app and a copy of stackql.exe were put in a folder the account could read and run from but not write to, which is what Program Files is to an ordinary account, and the app was started with that folder as its working folder. It started the engine beside it, the engine's data folder was under the app data directory, and nothing was added to the folder of the app.

Not run: the real Program Files, which needs an administrator, and a machine that truly has no WebView2 runtime.

Questions for the maintainer

  • Where an installed app keeps the engine's provider cache. It goes to the app data directory, which on Windows is in the roaming profile. A cache of two providers measured 95 MB. The local app data directory is the usual place for a cache.
  • Whether an installed app shares the provider cache of the stackql command shell the MSI installs, which is .stackql in the home folder. Today each has its own, so a provider installed in one is not seen in the other.

Generated with Claude Code

What was run after the check for a missing WebView2 runtime went in:

- The optimised build from CI, with the loader pointed at an empty
  folder, showed the app's own dialog and no terminal, and exited with
  code 1 when the dialog was closed. A click on the link brought
  Microsoft's page up in the browser.
- The app and an engine in a folder the account could not write to,
  which is what Program Files is to an ordinary account. The engine
  beside the app was started, its data folder was under the app data
  directory, and nothing was added to the folder of the app.

Two questions for the maintainer came out of the second: whether the
provider cache of an installed app belongs in the roaming profile, and
whether it should be the one the stackql command shell uses.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@jeffreyaven
jeffreyaven marked this pull request as ready for review November 20, 2026 05:57
@jeffreyaven
jeffreyaven merged commit 5740745 into main Nov 20, 2026
7 checks passed
@jeffreyaven
jeffreyaven deleted the installed-state-notes branch November 20, 2026 06:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant