superbol build tasks - missing cobc configuration

[GitMensch]

I do see a lot of configurations in package.json - but the nightly superbol-vscode-platform-0.1.5-linux-x64-debug.vsix only brings in 7 settings - and none about the cobc or lsp path (and I get "cobc not found" errors because there is none in PATH).

Where's the error?

[nberth]

I've checked the latest nightly, and did not see any issue with its settings. Could you provide us with a link to the faulty VSIX artefact?

[GitMensch]

I've used the linux one from https://github.com/OCamlPro/superbol-studio-oss/actions/runs/12953097992 and then go to settings for superbol - only 7 settings there - how much should there be?

[nberth]

Normally there's a dozen settings. Could you try with artifacts from the latest build https://github.com/OCamlPro/superbol-studio-oss/actions/runs/13035317124?

You may also try the "universal" extension in a REH, actually ;-)

[GitMensch]

checked locally with the linux one (remote workspace), then tried on gitpod (the linux one failed with the LSP because of glibc, but the universal worked out of the box), then even started a vscodium in windows and installed that version - in all environments (three different environments and use cases) going to user settings ans query for superbol I get exactly 7 configurations.

[nberth]

checked locally with the linux one (remote workspace), then tried on gitpod (the linux one failed with the LSP because of glibc, but the universal worked out of the box), then even started a vscodium in windows and installed that version - in all environments (three different environments and use cases) going to user settings ans query for superbol I get exactly 7 configurations.

Hum that's weird… I see 4 out of 11 settings have scope: "machine" or scope: "machine-overridable" (including cobc's path). May those not show up in settings view in some circumstances?