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

✨ Add grace period to reach LAPI without blocking further queries #153

Conversation

mathieuHa
Copy link
Collaborator

No description provided.

bouncer.go Outdated Show resolved Hide resolved
bouncer.go Outdated Show resolved Hide resolved
isCrowdsecStreamHealthy = false
bouncer.log.Error(fmt.Sprintf("handleStreamTicker:error updateFailure:%d %s", updateFailure, err.Error()))
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

why not use the same format of logs as just below ?

@maxlerebourg maxlerebourg merged commit ee97250 into main May 1, 2024
15 checks passed
@maxlerebourg maxlerebourg deleted the 152-feature-allow-users-to-specify-plugin-behavior-on-cache-refreshing-failure branch May 17, 2024 14:01
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.

[FEATURE] Allow users to specify plugin behavior on cache refreshing failure
2 participants