search

osate / osate2

Open Source AADL2 Tool Environment
http://osate.org
Eclipse Public License 2.0
39 stars 8 forks source link

units unresolved randomly #731

Closed juli1 closed 6 years ago

juli1 commented 8 years ago

Working on OSATE since several hours and randomly, the time units are no longer recognized. This is totally random, I have no reliable way to reproduce this. But this is very inconvenient and impact the user experience.

reteprelief commented 8 years ago

I have it too. It happens quite regularly on the Aircraft model that I brought over from the SAVI POC into AADL V2.

lwrage commented 8 years ago

I've seen that, too. For me it has always resolved itself after saving or modifying the file. I guess it's related to us using a hand-written name resolver instead of the scoping mechanism for linking.

lwrage commented 8 years ago

Copied form #749:

It is not uncommon when starting OSATE to find many Problems of the form

Couldn't resolve reference to UnitLiteral 'ms'. Couldn't resolve reference to property definition 'Latency'. Property set name may be missing.

Repeated Project Clean... can often resolve this, but the result is nondeterministic. Sometimes 100 errors occur, sometimes a dozen, and often (but not always) it clears them all.

lwrage commented 6 years ago

duplicate of #1009