-
Notifications
You must be signed in to change notification settings - Fork 9
2493 fix callback bugs for reducing in lb subcomponent #2494
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
Merged
lifflander
merged 2 commits into
develop
from
2493-fix-callback-bugs-for-reducing-in-lb-subcomponent
Nov 12, 2025
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -109,6 +109,51 @@ void CallbackRawBaseSingle::serialize(SerializerT& s) { | |||||
| s | cb_ | pipe_; | ||||||
| } | ||||||
|
|
||||||
| template <typename... Args> | ||||||
| template <typename... Params> | ||||||
| void CallbackTyped<Args...>::sendTuple(std::tuple<Params...> tup) { | ||||||
| using Trait = CBTraits<Args...>; | ||||||
| using MsgT = messaging::ParamMsg<typename Trait::TupleType>; | ||||||
| auto msg = vt::makeMessage<MsgT>(); | ||||||
| msg->setParams(std::move(tup)); | ||||||
| CallbackRawBaseSingle::sendMsg<MsgT>(msg); | ||||||
| } | ||||||
|
|
||||||
| template <typename... Args> | ||||||
| template <typename... Params> | ||||||
| void CallbackTyped<Args...>::send(Params&&... params) { | ||||||
| using Trait = CBTraits<Args...>; | ||||||
| if constexpr (std::is_same_v<typename Trait::MsgT, NoMsg>) { | ||||||
| // We have to go through some tricky code to make the MsgProps case work | ||||||
| // If we use the type for Params to send, it's possible that we have a | ||||||
| // type mismatch in the actual handler type. A possible edge case is when | ||||||
| // a char const* is sent, but the handler is a std::string. In this case, | ||||||
| // the ParamMsg will be cast incorrectly during the virual dispatch to a | ||||||
| // collection because callbacks don't have the collection type. Thus, the | ||||||
| // wrong ParamMsg will be cast to which requires serialization, leading to | ||||||
| // a failure. | ||||||
| if constexpr (sizeof...(Params) == sizeof...(Args) + 1) { | ||||||
| using MsgT = messaging::ParamMsg< | ||||||
| std::tuple< | ||||||
| std::decay_t<std::tuple_element_t<0, std::tuple<Params...>>>, | ||||||
| std::decay_t<Args>... | ||||||
| > | ||||||
| >; | ||||||
| auto msg = vt::makeMessage<MsgT>(); | ||||||
| msg->setParams(std::forward<Params>(params)...); | ||||||
| CallbackRawBaseSingle::sendMsg<MsgT>(msg); | ||||||
| } else { | ||||||
| using MsgT = messaging::ParamMsg<typename Trait::TupleType>; | ||||||
| auto msg = vt::makeMessage<MsgT>(); | ||||||
| msg->setParams(std::forward<Params>(params)...); | ||||||
| CallbackRawBaseSingle::sendMsg<MsgT>(msg); | ||||||
| } | ||||||
| } else { | ||||||
| using MsgT = typename Trait::MsgT; | ||||||
| auto msg = makeMessage<MsgT>(std::forward<Params>(params)...); | ||||||
| sendMsg(msg.get()); | ||||||
|
||||||
| sendMsg(msg.get()); | |
| CallbackRawBaseSingle::sendMsg<MsgT>(msg.get()); |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Corrected spelling of 'virual' to 'virtual'.