FactReference behaviour when dependency is skipped
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 6
- Avg merge
- 12h 25m
- Merged PRs (30d)
- 5
Description
If we have two resources ResourceA and ResourceB.
Where ResourceB requires ResourceA.
And we have a FactReference for ResourceB to ResourceA.
If ResourceA is skipped, the fact is not emitted and so the ResourceB fail.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the ResourceA/ResourceB scenario described in the issue and trace the FactReference handling when ResourceA is skipped. Identify where the fact emission is suppressed, then verify that ResourceB no longer fails and the expected fact is emitted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100