-
Notifications
You must be signed in to change notification settings - Fork 370
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
Set sender node id info with correct target lcid #2665
Conversation
Pull request automatically marked stale! |
@JanVogelsang: can you please comment on the status of this (and maybe merge master)? Thanks! |
Well, status is that I am waiting for a review. It's a rather small change and even a non-breaking one, but one that might help reduce errors in the future (as I had a bug in one of my branches because of this). |
f9efc88
to
e441a55
Compare
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.
Many thanks for this fix.
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.
Thanks for this improvement. Looks good to me.
In the
event_delivery_manager
thesender_node_id_info
is set during the event delivery using the samelcid
for all contiguous connections with the same source instead of the actual lcid of the connection. This is not wrong per se, but prevents us from grabbing the correct lcid lateron from theset_sender_node_id_info
. One could argue if that shouldn't be done at all, but why not. In NEST there is currently no use case in the kernel or any existing model, but it might potentially be used in NESTML or when users write their own models.Setting the correct lcid does not add any overhead and even reduces some redundancy in the code.