Staging instance, all changes can be removed at any time

Skip to content

cassandra: Bump next_visit_id when origin_visit_add is called by a replayer

When called by a replayer, the visit.visit field is set; but origin.next_visit_id was never incremented, so on the next loader run, the visit id would be 1 even if there is already a visit with that id.


Migrated from D6120 (view on Phabricator)

Merge request reports

Loading