-
Notifications
You must be signed in to change notification settings - Fork 207
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
Adding metadata endpoint #1049
Adding metadata endpoint #1049
Conversation
sdk/src/main/java/io/dapr/client/domain/SubscriptionMetadata.java
Outdated
Show resolved
Hide resolved
sdk/src/main/java/io/dapr/client/domain/SubscriptionMetadata.java
Outdated
Show resolved
Hide resolved
sdk/src/main/java/io/dapr/client/domain/SubscriptionMetadata.java
Outdated
Show resolved
Hide resolved
sdk/src/main/java/io/dapr/client/domain/SubscriptionMetadata.java
Outdated
Show resolved
Hide resolved
@artursouza there seems to be a flaky test with bindings and docker compose, but the code seems to be working as expected. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@salaboy I really like how you put everything together. I have left a few tiny comments.
@artursouza I have forked the repo here: https://github.com/artur-ciocanu/java-sdk. I tried to run the I was wondering if there is a way to run some of the workflow failing steps in isolation to figure out what should be adjusted to make it more robust. Thanks for your help! |
Hey @artur-ciocanu - Thanks for the review. You should be able to run what CI is running. So go to the examples directory and run the examples locally. It looks like its this test that is failing - see the README for instructions here I see |
sdk/src/main/java/io/dapr/client/domain/SubscriptionMetadata.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
few nits and a question, but generally the code looks good. Thanks @salaboy 🎉
6ae59cb
to
f6c5f27
Compare
@cicoyle @artursouza I have no idea why this is failing now. I can see this failing -> DaprClientGrpcTelemetryTest but the code in this PR hasn't changed anything there. |
2101fdf
to
732e7f1
Compare
Signed-off-by: salaboy <Salaboy@gmail.com>
Signed-off-by: salaboy <Salaboy@gmail.com>
Signed-off-by: salaboy <Salaboy@gmail.com>
Signed-off-by: salaboy <Salaboy@gmail.com>
Signed-off-by: salaboy <Salaboy@gmail.com>
Signed-off-by: salaboy <Salaboy@gmail.com>
Signed-off-by: salaboy <Salaboy@gmail.com>
Signed-off-by: salaboy <Salaboy@gmail.com>
Signed-off-by: salaboy <Salaboy@gmail.com>
Signed-off-by: salaboy <Salaboy@gmail.com>
Signed-off-by: salaboy <Salaboy@gmail.com>
Signed-off-by: salaboy <Salaboy@gmail.com>
Signed-off-by: salaboy <Salaboy@gmail.com>
Signed-off-by: salaboy <Salaboy@gmail.com>
Signed-off-by: salaboy <Salaboy@gmail.com>
Signed-off-by: salaboy <Salaboy@gmail.com>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1049 +/- ##
============================================
+ Coverage 76.91% 77.46% +0.55%
- Complexity 1592 1607 +15
============================================
Files 145 148 +3
Lines 4843 4908 +65
Branches 562 583 +21
============================================
+ Hits 3725 3802 +77
+ Misses 821 800 -21
- Partials 297 306 +9 ☔ View full report in Codecov by Sentry. |
You can run each step of the workflow manually, including the mechanical markdown script. It seems that the timeout increase did the trick. |
@holopin-bot @salaboy Thanks! |
Congratulations @salaboy, the maintainer of this repository has issued you a badge! Here it is: https://holopin.io/claim/clzva9l2k06280dlfe716ycjb This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account. |
Description
Adding metadata endpoint on HTTP and gRPC clients. Please review and advice.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #1048
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: