Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Possible exception source in coalescing_message_handler #1662

Closed
K-ballo opened this issue Jul 16, 2015 · 0 comments
Closed

Possible exception source in coalescing_message_handler #1662

K-ballo opened this issue Jul 16, 2015 · 0 comments
Labels
category: parcel transport type: defect
Milestone
0.9.11

Comments

@K-ballo
Copy link
Member

K-ballo commented Jul 16, 2015

There's a possibility for an exception to be thrown in coalescing_message_handler::flush if l.unlock() is hit twice. If the semantics prevent this from ever happening it should be clarified, otherwise it shall be fixed.
@hkaiser hkaiser added this to the 0.9.11 milestone Jul 16, 2015
sithhell added a commit that referenced this issue Jul 30, 2015
@sithhell
Merge pull request #1692 from STEllAR-GROUP/fixing_1662
5159a38 
Fixed #1662: Possible exception source in coalescing_message_handler
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
category: parcel transport type: defect
Projects
None yet
Milestone
0.9.11
Development

No branches or pull requests
2 participants
@hkaiser @K-ballo