You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have not seen this happen myself, but there are several reports in Slack about that evaluating an expression in a namespace sometimes results in a no such var error, where the var is from a required namespace, even though the var has previously been evaluated. The user then has to evaluate namespaces from the bottom up to get things working again.
I have created a test project for experimenting with trying to reproduce this issue:
I doubt this is an issue originating in Calva, but it could of course be. Please help with chasing this issue down. There are some little more instructions in that test project.
The text was updated successfully, but these errors were encountered:
I have not seen this happen myself, but there are several reports in Slack about that evaluating an expression in a namespace sometimes results in a
no such var
error, where the var is from a required namespace, even though the var has previously been evaluated. The user then has to evaluate namespaces from the bottom up to get things working again.I have created a test project for experimenting with trying to reproduce this issue:
I doubt this is an issue originating in Calva, but it could of course be. Please help with chasing this issue down. There are some little more instructions in that test project.
The text was updated successfully, but these errors were encountered: