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

[BUG] Threat intel alerts update requires locking to avoid conflict exceptions due to fan out #1177

Open
eirsep opened this issue Jul 18, 2024 · 2 comments
Open

[BUG] Threat intel alerts update requires locking to avoid conflict exceptions due to fan out #1177

eirsep opened this issue Jul 18, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@eirsep
Copy link
Member

eirsep commented Jul 18, 2024

Similar to findings, alert updates should be done with locking to avoid duplicate alerts and updation of alerts from fan out nodes failing due to concurrent updates.
@eirsep eirsep added bug Something isn't working untriaged labels Jul 18, 2024
@eirsep
Copy link
Member Author

eirsep commented Jul 18, 2024

#1176 is on similar lines

@dblock dblock removed the untriaged label Aug 5, 2024
@dblock
Copy link
Member

dblock commented Aug 5, 2024

[Catch All Triage - 1, 2, 3]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dblock @eirsep