Skip to content
This repository was archived by the owner on May 31, 2025. It is now read-only.

fixed UDP block number when EAGAIN or EWOULDBLOCK#957

Merged
jspricke merged 3 commits intoros:kinetic-develfrom
minsuu:kinetic-devel
Jan 16, 2017
Merged

fixed UDP block number when EAGAIN or EWOULDBLOCK#957
jspricke merged 3 commits intoros:kinetic-develfrom
minsuu:kinetic-devel

Conversation

@minsuu
Copy link
Copy Markdown
Contributor

@minsuu minsuu commented Jan 9, 2017

I found a bug in TransportUDP::write. When this branch is taken, num_bytes is initialized to retry the write operation. However, this_block stays increased. This causes block number in the datagram head to increase to an arbitrary amount, and the subscriber cannot receive the expected block. This commit just decreases this_block and retry the write properly.

@jspricke
Copy link
Copy Markdown
Member

+1, but could you remove the unrelated whitespace changes from the patch?

reverted unnecessary whitespace changes
@jspricke jspricke merged commit 0247de4 into ros:kinetic-devel Jan 16, 2017
@jspricke
Copy link
Copy Markdown
Member

Thx!

ggallagher01 pushed a commit to clearpathrobotics/ros_comm that referenced this pull request Jan 26, 2017
* fixed UDP block number when EAGAIN or EWOULDBLOCK
dirk-thomas pushed a commit that referenced this pull request Mar 2, 2017
* fixed UDP block number when EAGAIN or EWOULDBLOCK
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants