Peter Thomas

all: fixed. it would be great if you can validate latest `develop` solves this. so the only case where the http-builder can "retain state" is from the `Background` and for...

@CleanHit thanks, I really appreciate the simple example

@CleanHit thanks for the hints, it helped. is fixed in `develop`

@CleanHit thank you ! we follow a (what I realize may be a non-typical) process where we mark as `fixed` and close when the final non-RC release goes out, release...

@edwardsph upgraded and a couple of things broke, which don't look too bad, but please check with your suites when you get a chance. 2 tests have been commented out...

CI failed: ``` Error: Failures: Error: PaymentServiceContractTest.testPaymentService:33 Multi threaded access requested by thread Thread[main,5,main] but is not allowed for language(s) js. classpath:mock/contract/payment-service.feature:17 ```

just realized Graal 22.1 requires Java 11 ! https://github.com/oracle/graaljs/blob/master/CHANGELOG.md#version-2210 glad the build is set up to detect these problems: ``` Error: COMPILATION ERROR : [INFO] ------------------------------------------------------------- Error: /karate/karate-e2e-tests/src/test/java/driver/JavaApiRunner.java:[33,60] cannot access...

@edwardsph I think you will be able to use the latest version of graal without any issues by adding these to your `pom.xml` and over-ride. Karate never shades these JARs...

@packleader thanks ! I agree with your assessment, and 1.2.0 is a pretty solid release. I think creating a branch for 1.2.0 is the way to go. for now, I...

all: 1.2.1.RC2 should be in maven central now using graal-js 22.0