superbol-studio-oss icon indicating copy to clipboard operation
superbol-studio-oss copied to clipboard

superbol build tasks - missing cobc configuration

Open GitMensch opened this issue 11 months ago • 7 comments

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?

GitMensch avatar Jan 29 '25 08:01 GitMensch

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?

nberth avatar Jan 29 '25 10:01 nberth

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?

GitMensch avatar Jan 29 '25 14:01 GitMensch

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 ;-)

nberth avatar Jan 29 '25 16:01 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.

GitMensch avatar Jan 29 '25 21:01 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.

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?

nberth avatar Jan 29 '25 22:01 nberth

checked with the windows machine and currently nightly:

  • 7 settings under "user config->cobol", including Cobc-path (I guess the UI always upper-cases the first word)
  • going via extensions->settings, I get 11 ones - the reason: "SuperBOL" does not include "cobol", and 4 settings don't have '"COBOL" in their description, so they aren't found

Consider this mainly as a layer-8 issue... feel free to close this issue as "not planned" (because the report is invalid) or close it with a commit that adds "COBOL" to the 4 settings' description currently not including it (lsp-path, cache-in-global-storage, display-variable-attributes, gdb-path).

GitMensch avatar Mar 20 '25 11:03 GitMensch

So, how will this be resolved? Closed as invalid or "fixed" by a PR that adds "COBOL" in the setting descriptions, that currently don't have that?

GitMensch avatar May 23 '25 17:05 GitMensch

Thanks for the reminder about this issue. I figured we can simply add a list of keywords as comments in descriptions, so this issue will be fixed.

nberth avatar May 26 '25 08:05 nberth