Skip to content

Conversation

@MaximilianToe
Copy link
Contributor

This pull request provides the following:

  • An interface for a USubscriptionClient in USubscription.h
  • An Implementation of that interface in RpcClientUSubscription.cpp/RpcClientUSubscription.h
  • A template method InvokeProtoMethod to send and receive requests with a specific payload type in RpcClient.h similar to the one present in up-rust
  • A helper request builder and uuri builder
  • Extracting part of Consumer.cpp that was also needed for USubscription to avoid code duplication

@github-actions
Copy link

github-actions bot commented Jun 9, 2025

Code coverage report is ready! 📈

Copy link
Contributor

@PLeVasseur PLeVasseur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @MaximilianToe -- thanks for contributing!

I noted more up-spec-related items and have tagged @sophokles73 and @stevenhartley onto the PR as there may be gaps in the spec (or in my understanding of it!)

@github-actions
Copy link

Code coverage report is ready! 📈

@sophokles73
Copy link

@PLeVasseur would you mind taking another look?

@PLeVasseur
Copy link
Contributor

Yup, will do. Try to make it fit this week 👍

Copy link
Contributor

@PLeVasseur PLeVasseur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the updates @MaximilianToe! Can you take a look at the comments I left?

It feels to me there's still a bit of alignment work to ensure that the C++ RpcClient API mimics the Rust equivalent. Happy to hear your thoughts.

@MaximilianToe MaximilianToe force-pushed the RpcClientUSubscription branch from 701bfdf to 6aae8ea Compare August 11, 2025 19:45
@github-actions
Copy link

Code coverage report is ready! 📈

@github-actions
Copy link

Code coverage report is ready! 📈

@MaximilianToe MaximilianToe force-pushed the RpcClientUSubscription branch from 2d22bb9 to 3b8a7ca Compare August 24, 2025 16:37
@github-actions
Copy link

Code coverage report is ready! 📈

@MaximilianToe MaximilianToe force-pushed the RpcClientUSubscription branch from 3b8a7ca to 4375d15 Compare August 24, 2025 16:45
@github-actions
Copy link

Code coverage report is ready! 📈

@github-actions
Copy link

Code coverage report is ready! 📈

@MaximilianToe MaximilianToe force-pushed the RpcClientUSubscription branch from ccb349b to 15e8bcb Compare August 24, 2025 17:44
@github-actions
Copy link

Code coverage report is ready! 📈

@MaximilianToe MaximilianToe force-pushed the RpcClientUSubscription branch from 15e8bcb to 0c41572 Compare August 24, 2025 17:59
@github-actions
Copy link

Code coverage report is ready! 📈

@MaximilianToe MaximilianToe force-pushed the RpcClientUSubscription branch from 0c41572 to c8fdce4 Compare August 24, 2025 19:01
@github-actions
Copy link

Code coverage report is ready! 📈

@MaximilianToe MaximilianToe force-pushed the RpcClientUSubscription branch from c8fdce4 to f899ee8 Compare August 24, 2025 19:05
@github-actions
Copy link

Code coverage report is ready! 📈

Copy link
Contributor

@PLeVasseur PLeVasseur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @MaximilianToe -- thanks for troubleshooting the thread-safety issue. Let's merge this then

@PLeVasseur
Copy link
Contributor

@sophokles73 -- hmm, have we made a change recently to how the repos are set up?

As far as I can see from the .eclipsefdn repo's up-cpp portion I don't see two approvals as needed. 🤔

@sophokles73
Copy link

@sophokles73 -- hmm, have we made a change recently to how the repos are set up?

As far as I can see from the .eclipsefdn repo's up-cpp portion I don't see two approvals as needed. 🤔

I did indeed make a change to the org configuration but that should only have resulted in merge commits no longer being allowed ... I'll try to see if I can find out anything. Maybe the EF has made some corresponding general config change to all its orgs?

@PLeVasseur
Copy link
Contributor

@sophokles73 -- hmm, have we made a change recently to how the repos are set up?
As far as I can see from the .eclipsefdn repo's up-cpp portion I don't see two approvals as needed. 🤔

I did indeed make a change to the org configuration but that should only have resulted in merge commits no longer being allowed ... I'll try to see if I can find out anything. Maybe the EF has made some corresponding general config change to all its orgs?

Okay -- I'll ask about this on Slack 🫡

@sophokles73
Copy link

Okay -- I'll ask about this on Slack 🫡

I have already created a PR to reduce the number of required reviews to 1 again ...

@PLeVasseur
Copy link
Contributor

Okay -- I'll ask about this on Slack 🫡

I have already created a PR to reduce the number of required reviews to 1 again ...

Thanks! It does still seem to show as needing two reviews on this one tho 🤔

image

Is there some lingering effect on already-existing PRs or something like that?

@sophokles73
Copy link

Okay -- I'll ask about this on Slack 🫡

I have already created a PR to reduce the number of required reviews to 1 again ...

Thanks! It does still seem to show as needing two reviews on this one tho 🤔

image Is there some lingering effect on already-existing PRs or something like that?

Maybe, I don't know. Anyway, I will simply approve this PR now and then you can squash and merge it ...

Copy link

@sophokles73 sophokles73 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@PLeVasseur PLeVasseur merged commit 91b6eec into eclipse-uprotocol:main Sep 9, 2025
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants