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
On the other hand, if we use the flow identifier and a state, the FHA generation works. For example, the examples in https://github.com/osate/examples/tree/master/error-model/FHA are working but they use only the error source with a reference to the error state, not the error type.
The text was updated successfully, but these errors were encountered:
Sounds to be related to the stack mechanism to retrieve properties.
Probably something around EMV2Properties in isErrorModelElementProperty or matchCIStack
When generating the FHA, nothing is generated when using an error type on the error source feature. Please have a look at the following project: https://github.com/osate/examples/tree/master/error-model/lifevest
And particularly at this file: https://github.com/osate/examples/blob/master/error-model/lifevest/visibility.aadl
On the other hand, if we use the flow identifier and a state, the FHA generation works. For example, the examples in https://github.com/osate/examples/tree/master/error-model/FHA are working but they use only the error source with a reference to the error state, not the error type.
The text was updated successfully, but these errors were encountered: