Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ensure exceptions during CatchUpHook are properly handled #4908

Open
mhsdesign opened this issue Feb 21, 2024 · 1 comment
Open

Ensure exceptions during CatchUpHook are properly handled #4908

mhsdesign opened this issue Feb 21, 2024 · 1 comment
Labels
9.0 Bug

Comments

@mhsdesign
Copy link
Member

Currently any faulty catchup implementation can prevent a replay.
As they are rather optional, maybe the should not crash the whole system?

flow cr:replayAll       
Replaying events for all projections of Content Repository "default" ...
The node type "Foo:Document.Starship" is not available

  Type: Neos\ContentRepository\Core\SharedModel\Exception\NodeTypeNotFoundException
  Code: 1316598370
  File: Packages/Neos/Neos.ContentRepository.Core/Classes/NodeType/NodeTypeManager.
        php
  Line: 126
@bwaidelich bwaidelich mentioned this issue Apr 15, 2024
Open
@bwaidelich
Copy link
Member

This can hopefully be simplified a lot with #4992

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
9.0 Bug
Projects
Neos 9.0
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bwaidelich @mhsdesign