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.

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

Check that last seen event ID exists while emitting the event feed #2695

Merged
merged 1 commit into from
Sep 25, 2024

Conversation

eldering
Copy link
Member

This will throw an error, for example, when the database gets reloaded while there is a running process serving the event feed to a connected client. We encountered this problem at WF Astana.

This will throw an error, for example, when the database gets
reloaded while there is a running process serving the event feed
to a connected client. We encountered this problem at WF Astana.
throw new HttpException(500, sprintf('Cannot find event %d in database anymore', $lastIdSent));
}
// Remove the previously last sent event. We just fetched
// it to make sure it's there.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// it to make sure it's there.
// it to make sure it's still there.

@eldering eldering added this pull request to the merge queue Sep 25, 2024
Merged via the queue into main with commit ef8c832 Sep 25, 2024
30 checks passed
@eldering eldering deleted the fix-eventfeed-db-reload branch September 25, 2024 22:22
Copy link

sentry-io bot commented Sep 29, 2024

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

  • ‼️ Symfony\Component\HttpKernel\Exception\HttpException: Cannot find event 0 in database anymore /src/Controller/API/ContestController.php in Ap... View Issue

Did you find this useful? React with a 👍 or 👎

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants