route:update events have a Vehicle argument?

[faultyserver]

I recently noticed this event come through:

#<Shark::Event:0x007fd9c3f12eb8
  @topic="routes.1B",
  @type=:update,
  @args=[
    #<Shark::Vehicle:0x007fd9c2946828
      @associated_objects={},
      @name="4008",
      ...
    >
  ],
  @kwargs={},
  @originator="vehicles.4008"
>

That is, an :update event to a Route topic is being passed a Vehicle argument instead of the Route that is being updated. Note that the argument being passed is the Vehicle that originated the event, meaning this is likely an issue with how Conductor is publishing these events.

[faultyserver]

Turns out this was just a mistake in the REPL code. I was using last :update, to: 'routes.1B', which in turn ran this line:

@events[to].find{ |event| event.type = type }

Having the single = in the find condition meant that the latest event (no matter the type; in this case a :vehicle_update, where a Vehicle argument makes sense) would always be taken.