Change Details

Instead of failing the replay, log the unfit origin_visit (because too old format) and continue the replay. This aligns the behavior with other methods (skipped unfit revision, skipped colliding hash, etc...). This also format the warning message as other object insertion do (revision, content, etc...). Depends on D2838

Also clarify the crash behavior which is an expected one. If an origin_visit is too old (without type), this is unexpected. So the replayer must crash and we must fix the journal's origin_visit topic. This now definitely says as much in the code.

Instead of failingAlso clarify the replay, log the unfit origin_visit (because too oldcrash behavior which is an expected one. format) and continue the replay.If an origin_visit is too old (without type), Tthis aligns the behavior with other methods (skippedis unexpected. unfit revision, skipped colliding hash, etc...)So the replayer must crash and we must fix the journal's origin_visit topic. This also format the warning message as other object insertion do (revision, content, etc...). Depends on D2838now definitely says as much in the code.