goals not displayed

[gares]

I've a trace where goals are "undefined",

trace.zip

But actually, I believe the trace is not special, since even trivial examples have the same bug. Hence I suspect it is related to my setup. This is VSCode

Version: 1.74.3
Commit: 97dec172d3256f8ca4bfb2143f3f76b503ca0534
Date: 2023-01-09T16:57:40.428Z
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Linux x64 5.15.0-56-generic snap
Sandboxed: No

CC @jwintz

[jwintz]

First test on macOS, can't reproduce (using trace_chr however). Most versions match.

Version: 1.74.3 (Universal)
Commit: 97dec172d3256f8ca4bfb2143f3f76b503ca0534
Date: 2023-01-09T17:07:18.579Z (1 wk ago)
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Darwin arm64 22.2.0
Sandboxed: No

I'll test on linux right now.

In the meantime, could you please provide the output of the console from the embedded developer tools if anything relevant ?

[jwintz]

As for the attached trace, no issue either.

[jwintz]

Same goes for linux.

[jwintz]

Waiting for more input on the console logs.

[gares]

It seems to be related to the syntax highlighting setting, if I change it then it works:

[jwintz]

I have performed all the previous tests with synatx highlighting set as well. It surely takes forever for the message mecanism to provide the formatted output for each LHS card as well as for the RHS displayed card when it comes to a large trace, but it works. Could U try to load the trace and let it be for a while just to make sure formatted output gets displayed at some point ? We could then try to order message sending starting with the currently displayed cards.

Note: This is still an unsatisfactory fallback waiting for VSCode internals WRT/ syntax highlighting being exposed through the extension API ....

[gares]

I don't know what is going on, but here it is reproducible. I'm on a new PC with elpi-lang 0.2.4 downloaded from the store.

Screencast.from.25-01-2023.11.07.07.webm

I did not see any weird message in the JS console, so I'm really clueless.

[ThomasPortet]

I had the same problem and it got solved by disabling the syntax highlight option as well. Also the first time I clicked on watch it didn't work but I can't reproduce it so I'm not sure what happened there. Here's my VS version if it helps

Version: 1.75.1
Commit: 441438abd1ac652551dbe4d408dfcec8a499b8bf
Date: 2023-02-08T21:35:30.018Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: 10.2.154.23-electron.0
OS: Linux x64 5.4.0-77-generic snap
Sandboxed: Yes