tlaplus / tlaplus/CommunityModules
Host and Clock from ShiViz module do not appear in error trace
Nobody has claimed this yet.
- Dominant language
- TLA
- Stars
- 315
- Forks
- 48
- Avg merge
- 13h 27m
- Merged PRs (30d)
- 2
Description
As suggested in https://github.com/tlaplus/CommunityModules/issues/37#issuecomment-810576974 I tried using ALIAS to make Host and Clock from the ShiViz module appear in the error trace. While ALIAS works in principle, it seems to get ignored as soon as I add Host or Clock:
---- CONFIG testAlias ----
SPECIFICATION Spec
INVARIANT NotTwo
ALIAS Alias
======================
----------------------------- MODULE testAlias -----------------------------
EXTENDS Integers, ShiViz
(*--algorithm testAlias
variables x=0;
begin
x := 1;
x := 2;
end algorithm; *)
\* BEGIN TRANSLATION (chksum(pcal) = "b3726e35" /\ chksum(tla) = "e9b2f587")
VARIABLES x, pc
vars == << x, pc >>
Init == (* Global variables *)
/\ x = 0
/\ pc = "Lbl_1"
Lbl_1 == /\ pc = "Lbl_1"
/\ x' = 1
/\ pc' = "Lbl_2"
Lbl_2 == /\ pc = "Lbl_2"
/\ x' = 2
/\ pc' = "Done"
(* Allow infinite stuttering to prevent deadlock on termination. *)
Terminating == pc = "Done" /\ UNCHANGED vars
Next == Lbl_1 \/ Lbl_2
\/ Terminating
Spec == Init /\ [][Next]_vars
Termination == <>(pc = "Done")
\* END TRANSLATION
NotTwo == x /= 2
Alias == [
test |-> x + 2,
Host |-> Host
]
=============================================================================
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the testAlias specification and its ALIAS configuration, reproducing the error trace with Host and Clock included. Compare the trace with the working test alias, then verify that Host and Clock appear as expected when the issue is resolved.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100