-
Notifications
You must be signed in to change notification settings - Fork 32
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
Unable to run karate-grpc - generation of protobuf descriptor sets fails #10
Comments
hi, @vinamrajais , sorry for replying so late, I will the next two week solve these issue, thanks! |
Thank you! I am seeing the same error. |
[ERROR] Failed to execute goal on project karate-grpc-helper: Could not resolve dependencies for project com.github.thinkerou:karate-grpc-helper:jar:1.0.3: Failed to collect dependencies at com.github.thinkerou:karate-grpc-core:jar:1.0.3: Failed to read artifact descriptor for com.github.thinkerou:karate-grpc-core:jar:1.0.3: Failure to find com.github.thinkerou:karate-grpc-parent:pom:1.0.3 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1] I am also getting this error |
We just started investigating Karate for testing our REST APIs. It looks like it's going to be a great fit alongside our Selenium tests. One of our teams has implemented their newest API using gRPC, instead of REST. I'm going to take a look at grpc-cucumber-js, but that would mean three totally different frameworks and languages for our tests. I was excited to see that thre is an effort to enable Karate to test gRPC APIs, but I'm seeing the same error as @vinamrajais and @jeetendrae. |
@nathanchilton you can check out this project and |
Does anyone has a solution for this? I am seeing exactly same issue. thanks! |
@thinkerou Has this issue been resolved yet? |
https://repo.maven.apache.org/maven2/com/github/thinkerou/karate-grpc-helper/1.0.3 does not exist!!
The text was updated successfully, but these errors were encountered: