callSingle update

[OreOreDa]

Description

When performing "karate.configure('callSingleCache', { minutes: 15 })", some users would expect the feature to be executed again every 15min when doing "karate.callSingle(feature, args)"

• Relevant Issues : The feature executed once by "callSingle" is not executed again when using "callSingleCache"
• Relevant PRs
  • Type of change :
  • New feature
  • Bug fix for existing feature
  • Code quality improvement
  • Addition or Improvement of tests
  • Addition or Improvement of documentation

[ptrthomas]

@OreOreDa sorry I don't understand the logic so I request someone with more time to review. I consider doing the cache check outside the synchronized block important as an optimization and I don't like changing that

[OreOreDa]

@ptrthomas The thing is, if there is a cache hit right away, you don't get a chance to test the cache file and renew it - and the cache file check has to be done in the synchronized block
Maybe we could do the check outside the synchronized block only if "minutes" is zero (i.e. no "callSingleCache" is used) ?

[OreOreDa]

@ptrthomas I updated my PR, thanks!