Rpc client u subscription#324
Conversation
|
Code coverage report is ready! 📈
|
PLeVasseur
left a comment
There was a problem hiding this comment.
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!)
include/up-cpp/client/usubscription/v3/RpcClientUSubscription.h
Outdated
Show resolved
Hide resolved
|
Code coverage report is ready! 📈
|
|
@PLeVasseur would you mind taking another look? |
|
Yup, will do. Try to make it fit this week 👍 |
PLeVasseur
left a comment
There was a problem hiding this comment.
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.
701bfdf to
6aae8ea
Compare
|
Code coverage report is ready! 📈
|
|
Code coverage report is ready! 📈
|
2d22bb9 to
3b8a7ca
Compare
|
Code coverage report is ready! 📈
|
3b8a7ca to
4375d15
Compare
|
Code coverage report is ready! 📈
|
|
Code coverage report is ready! 📈
|
ccb349b to
15e8bcb
Compare
|
Code coverage report is ready! 📈
|
15e8bcb to
0c41572
Compare
|
Code coverage report is ready! 📈
|
0c41572 to
c8fdce4
Compare
|
Code coverage report is ready! 📈
|
# Conflicts: # include/up-cpp/communication/RpcClient.h
c8fdce4 to
f899ee8
Compare
|
Code coverage report is ready! 📈
|
PLeVasseur
left a comment
There was a problem hiding this comment.
Hi @MaximilianToe -- thanks for troubleshooting the thread-safety issue. Let's merge this then
|
@sophokles73 -- hmm, have we made a change recently to how the repos are set up? As far as I can see from the |
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 🫡 |
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 🤔
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 ... |


This pull request provides the following: