Blocker: TLA+ model checking (web) view not populated when model-checking again
See original GitHub issueOn Windows (and Linux) with VSCode newer than 1.46.1
and any version of this extension in 1.5.0..1.5.1-alpha-2
, re-running model-checking results in an empty web view (iff the web view gets closed in between). The Windows task manager confirms that TLC spawns and terminates correctly.
(Downgrading to VSCode 1.46.1 reliably fixes the issue)
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
TLA+ Model Checking Made Symbolic - Archive ouverte HAL
The user has to annotate the records and their sets with a super type, e.g., [type : Name, rm : Set[Name]]. 4 KERA+:...
Read more >Entry-level Model Checker Tutorial - Apalache Documentation
This predicate describes the transitions of our state machine. Again, there are no variables and Next == TRUE , so this transition defines...
Read more >Checking a Model - TLA+
You can view the progress of the run on the model editor's Model Checking Results Page. That page is automatically displayed when TLC...
Read more >Model Checking TLA+ Specifications - Leslie Lamport
and ZF set theory. TLC is a new model checker for debugging a TLA. + specification by checking invariance properties of a finite-state...
Read more >Introduction to TLA+ Model Checking in the Command Line
Otherwise known as “wait, you mean I can use the TLA toolbox from the command line?” Designed by Freepik. I started playing around...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@lemmy, here’s a pre-release with the issue solved: v1.5.1-beta.1
Update: And here’s the release: v1.5.1
Fixed in v1.5.1. Please, reopen the issue if the problem still remains in your environment.