-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retry until issue #1662
Comments
@XoNems please follow this process and we will investigate. but you HAVE to follow the process: https://github.com/intuit/karate/wiki/How-to-Submit-an-Issue |
Hello, I understand the process. However my reproduction case will not be so easy from a public API. It's pretty straightforward. In 0.96: In 1.0.0: Here are the console logs
Regard |
@XoNems not reading the above.
that's exactly what mocks are for. if this issue is important to you, you have to find the time. refer this example if needed: #1645 (comment) |
Hello here,
I have been using Karate since early 2019.
We use Karate to manage the non regression tests of a multi stack asynchronous datalake project.
Managing the retry is important to us.
I went from 0.96 (which was great) to 1.0.0 last Friday.
I had to make a lot of small changes but without much impact.
However I just realized a big change concerning the retry.
This call in 0.96 was viable:
And retry until responseStatus == 200 && response.lastMeasures [2!] = []
But since 1.0.0 I have an error and my retry does not seem to work anymore
java.lang.AssertionError: >>>> js failed:
01: responseStatus == 200 && response.lastEvents [2] .type! = Null
<<<<
org.graalvm.polyglot.PolyglotException: Index 2 out of bounds for length 2
I tried to find something on the internet but was unsuccessful, do you have a lead? Thank you in advance !
Regard
The text was updated successfully, but these errors were encountered: