Correctly handle count parameter @ HistoryDict.save_node_value
The current implementation is actually a no-op since the data is truncated correctly but not assigned back to self._datachanges. Pop the first value instead since this function is called for every datachange which means that not more than one value will every be removed in a single call.
Showing
Please register or sign in to comment