karate.jsonPath() Concurrency Bug

[josh-pius]

Bug Description

• When running tests that call karate.jsonPath() across multiple threads, karate.jsonPath() occasionally uses the JSON value passed in from another thread instead of the actual JSON passed to it
• The underlying cause seems to be coming from a library karate depends on internally, namely json-path. The underlying issue is a concurrency bug in json-path's internal caching mechanism. More details on this bug is reported by another user of this library JsonPath GH Issue

Replication

• Demo

[ptrthomas]

@josh-pius wow, thanks for reporting this.

to be honest I'm not a fan of json-path syntax and now advocate for using JS functions instead. for example this is the workaround I would use for your example:

* def result = json.find(x => x.ID === 1).VALUE

other JS patterns I recommend are found here: https://stackoverflow.com/a/76091034/143475