question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error-Trace Exploration can't resolve definitions in other modules

See original GitHub issue

Bug repro steps:

  1. Open below specs in the TLA Toolbox (tested in version 1.5.6 on Windows 10 64-bit)
  2. Create a model for the SystemMC spec
  3. Define MaxCounterValue as 5 (or any number you want), ensure deadlock is being checked
  4. Run TLC
  5. When deadlock is reached, open the Error-Trace Exploration window
  6. Add some expression to check (for example, MaxCounterValue)
  7. Click “Explore”; the following error box pops up, unable to find the definition of Null:

image

------------------------------- MODULE System -------------------------------

EXTENDS
    Naturals

VARIABLES
    Counter

-----------------------------------------------------------------------------

Null == CHOOSE n : n \notin Nat

TypeInvariant ==
    /\ Counter \in Nat \cup {Null}

Init ==
    /\ Counter = Null

FirstIncrement ==
    /\ Counter = Null
    /\ Counter' = 0

Increment ==
    /\ Counter /= Null
    /\ Counter' = Counter + 1

Next ==
    \/ FirstIncrement
    \/ Increment

=============================================================================
------------------------------ MODULE SystemMC ------------------------------

EXTENDS
    Naturals

CONSTANTS
    MaxCounterValue

VARIABLES
    Counter

ASSUME MaxCounterValue \in Nat

-----------------------------------------------------------------------------

S == INSTANCE System

TypeInvariant ==
    /\ S!TypeInvariant

Init ==
    /\ S!Init

Next ==
    IF Counter = S!Null
    THEN S!Next
    ELSE
        /\ Counter < MaxCounterValue
        /\ S!Next

=============================================================================

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:8 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
ahelwercommented, Dec 15, 2020

@lemmy I checked and can confirm that ALIAS-style trace expressions work perfectly when using definitions from other modules.

1reaction
lemmycommented, Sep 17, 2020

@ahelwer Can you check how this is handled by SpecTE?

Read more comments on GitHub >

github_iconTop Results From Across the Web

resolve-module-path doesn't load the module #4498 - GitHub
'errortrace) should be #t . However, the implementation of resolve-module-path doesn't ask module-path-index-resolve to load the module.
Read more >
Receiving 'Error: Can't resolve <custom_module_name ...
I am attempting to import a module that I have created locally and linked / installed to another module which is built and...
Read more >
Racket Mode
As a result, to find a definition, it is necessary to know exactly which identifier is meant — either by expanding the module...
Read more >
The TLA Toolbox - Leslie Lamport
View the pretty-printed versions of your modules. Run the TLC model checker. The Toolbox allows you to explorer an error trace produced by ......
Read more >
Error: Can't resolve '@nativescript/geolocation' | SAP Community
Hey all, Like others, I've been following the tutorial here: ... ModuleNotFoundError: Module not found: Error: Can't resolve ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found