You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The fix for #33 is not correct in the case of a StatelessWriter. If the publisher is configured with KEEP_LAST_HISTORY_QOS and BEST_EFFORT reliability, StatelessWriter::clean_history() always returns false now, which means that when it's called in PublisherHistory::add_pub_change(), it triggers the path that logs Attempting to add Data to Full WriterCache:.
Might be enough to return true from StatelessWriter::clean_history() instead.
The text was updated successfully, but these errors were encountered:
`PublisherHistory::add_pub_change()` calls `clean_history()` and considers history full if it returns false. Actually remove items from history, and return whether we actually removed anything.
for eProsima#34
The fix for #33 is not correct in the case of a
StatelessWriter
. If the publisher is configured with KEEP_LAST_HISTORY_QOS and BEST_EFFORT reliability,StatelessWriter::clean_history()
always returns false now, which means that when it's called inPublisherHistory::add_pub_change()
, it triggers the path that logsAttempting to add Data to Full WriterCache:
.Might be enough to return
true
fromStatelessWriter::clean_history()
instead.The text was updated successfully, but these errors were encountered: