DevOps-MBSE / AaC

Prototype Arch-as-Code
https://devops-mbse.github.io/AaC/
MIT License
27 stars 7 forks source link

🐛 Definitions not being parsed and added to context #841

Open jondavid-black opened 1 month ago

jondavid-black commented 1 month ago

Pre-requisites

What version of the AaC package are you using? Check your version with the command: aac version.

0.4.11

Description

When I parse a model with req traces I'm not getting a listing of all the defined reqs. There's nothing different or strange about how these are defined that I can see. But interestingly it is consistent, run after run the same reqs fail to be recognized.

Reproduction URL

No response

Reproduction steps

Parse the sample here:  https://github.com/DevOps-MBSE/aac-doc-mdl/blob/main/tests/samples/trade_study/doc/cookie_trade_study.aac

Get all the `req` items from the context and you'll see there are some missing items.

Screenshots

If applicable, add screenshots to help explain your problem.
![DESCRIPTION](LINK.png)

Logs

Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.

Pertinent Files

Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.

jondavid-black commented 1 month ago

First I should say that I pulled the latest 0.4.18 for this testing to avoid confusion.

I went ahead and created the parse-bug branch so that I could drop in a test case that demonstrates the issue.

You can run behave -i ./features/trade_study.feature --no-capture to see the issue...and it is weird.

When I parse the sample model, everything seems fine. I check all my counts and even every value and come out clean. But when I run the check it looks like values just "disappear" from the context and req.id references fail to check when I've already shown that they exist. Certainly more investigation to do here.