CLIRuleTests fail, because action is not found
- Dominant language
- Scala
- Stars
- 6.8k
- Forks
- 1.2k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 2
Description
In the last days we had the issue, that CLIRuleTests failed.
On looking into it, we realized, that the failed actions took old activations with the same name.
On looking into the old activations, that were probably taken, there is the error:
`failed to invoke action lime@us.ibm.com/A_421: not found on 'get'`
My assumption is, that this happens because of the eventually consistency of the database.
In the test, the action and the rule are created and invoked immediatly after creating.
I think an check, if the action is already there should be inserted.
Contributor guide
Research direction
Start with CLIRuleTests and trace the action and rule creation sequence before invocation. Confirm the action is available before it is invoked, then run CLIRuleTests to verify that the intermittent “not found” failure no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100