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

chore: setting ResourceAttemptsTimelockServiceError to warn instead o… #3265

Conversation

nicolasburtey
Copy link
Member

…f critical

@@ -81,7 +81,7 @@ export const idempotencyMiddleware = async (
fallbackMsg: "Error locking idempotency key",
level: ErrorLevel.Critical,
})
if (error instanceof ExecutionError) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we still need the try-catch in the lines above this if we're (correctly) doing this inside the lock service now?

Copy link
Member Author

Choose a reason for hiding this comment

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

you're right

@nicolasburtey nicolasburtey force-pushed the chore--setting-ResourceAttemptsTimelockServiceError-to-warn-instead-of-critical branch 2 times, most recently from 3c4b262 to cd959bb Compare September 25, 2023 11:11
@nicolasburtey nicolasburtey force-pushed the chore--setting-ResourceAttemptsTimelockServiceError-to-warn-instead-of-critical branch from cd959bb to 9a65b06 Compare September 25, 2023 20:21
@nicolasburtey nicolasburtey force-pushed the chore--setting-ResourceAttemptsTimelockServiceError-to-warn-instead-of-critical branch from 9a65b06 to dab8a0d Compare September 25, 2023 20:28
@nicolasburtey nicolasburtey merged commit fcd16d5 into main Sep 25, 2023
13 checks passed
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.

2 participants