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
The contraint in_range is now used in NFV examples, at least in Example-A-14 (from 2.8.1 onwards).
The corresponding outputs is given in the attached file.
This may be linked to :
alloy.py: elif value_type == 'range':
alloy.py- # TODO: value must be an integer else this is an error.
alloy.py- return str(value)
So it probably requires a few changes in alloy.py an TOSCA.als (pred in_range[]) (?) trace_issue05-1.txt
The text was updated successfully, but these errors were encountered:
The contraint in_range is now used in NFV examples, at least in Example-A-14 (from 2.8.1 onwards).
The corresponding outputs is given in the attached file.
This may be linked to :
alloy.py: elif value_type == 'range':
alloy.py- # TODO: value must be an integer else this is an error.
alloy.py- return str(value)
So it probably requires a few changes in alloy.py an TOSCA.als (pred in_range[]) (?)
trace_issue05-1.txt
The text was updated successfully, but these errors were encountered: