I ran a reasonably straightforward script on a codespace and in a locally running project template:
CONTEXT Issue1472
PURPOSE CONTEXT Issue1472
{+ There is an error in the Codespace deployment. I'm trying to reproduce it in a small script. +}
RELATION refer[Identifier*Entity] [TOT]
RELATION name[Identifier*Name] [UNI,TOT]
VIEW Identifier : Identifier(name)
INTERFACE Identifiers: "_SESSION";V[SESSION*Identifier] BOX
[ id : I
, name : name
, entity : refer
]
ENDCONTEXT
In the following script, I am removing the relation refer
CONTEXT Issue1472a
PURPOSE CONTEXT Issue1472a
{+ There is an error in the Codespace deployment. I'm trying to reproduce it in a small script. +}
RELATION name[Identifier*Name] [UNI,TOT]
VIEW Identifier : Identifier(name)
INTERFACE Identifiers: "_SESSION";V[SESSION*Identifier] BOX
[ id : I
, name : name
]
ENDCONTEXT
Now, this video shows the behaviour I get. Surprisingly, this is the desired behaviour.
What I expected
I expected both scripts to behave like the second one.
The experiment is still there, open for investigation.
I reproduced the experiment on a locally running project template and deployed it with docker, just to confirm my hunch that this has nothing to do with deployment. I believe we need a diagnosis first. My gut feeling is this has to do with bitrot.
What happened
I ran a reasonably straightforward script on a codespace and in a locally running project template:
The prototype does NOT behave as expected. Here is a video of the wrong behaviour.
In the following script, I am removing the relation
refer
Now, this video shows the behaviour I get. Surprisingly, this is the desired behaviour.
What I expected
I expected both scripts to behave like the second one.
Version of ampersand that was used
Steps to reproduce
I reproduced the experiment on a locally running project template and deployed it with docker, just to confirm my hunch that this has nothing to do with deployment. I believe we need a diagnosis first. My gut feeling is this has to do with bitrot.