Inaccurate vote sum displayed after voting until page is refreshed

I'm currently troubleshooting an issue (#1940644: Vote sum not displayed until page is refreshed) with an up/down widget with the 'points' value type.

The problem is that after the user votes, the widget appears to show only the value of the vote she cast, regardless of the sum, until the page is refreshed. When the page is refreshed, the correct sum is displayed (matching the VotingAPI cache table value for the 'sum' function for the entity being rated).

I'm still getting familiar with Rate module, but I noticed this block of code in rate_get_results(), which is called from rate_vote_ahah() via rate_generate_widget():

  foreach ($results as $result) {
    if ($widget->value_type == 'percent' && $result['function'] == 'average') {
      $output['rating'] = $result['value'];
    }
    elseif ($widget->value_type == 'points' && $result['function'] == 'sum') {
      $output['rating'] = $result['value'];
    }
    elseif ($result['function'] == 'count') {
      $output['count'] = $result['value'];
    }
    elseif (preg_match('/^option\\-([\\-0-9]+)$/', $result['function'], $match)) {
      $output['options'][$match[1]] = $result['value'];
      $output['count'] += $result['value'];
    }
  }

2 issues with this block of core are:

A) With the criteria specified here, VotingAPI returns 3 results: One for each value type (sum, count, average).

B) Since we're looping through doing $output['rating'] = $result['value']; each time, we're just overwriting the value.

My sense is we should store the desired default vote result function in the widget definition. Based on the README and the code flow, it appears that Rate intends to support the VotingAPI 'sum' function, however, "Average" is the only VotingAPI function listed for the "Which rating should be displayed" setting.

It would be great to get some validation from the Rate maintainer that this is in fact a bug and that we're not dealing with misconfiguration here :).