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

Classify more long response to timeout instead of 499 #23700

Merged
merged 7 commits into from
Feb 7, 2025

Conversation

zhangxin511
Copy link
Contributor

@zhangxin511 zhangxin511 commented Jan 30, 2025

Description

Some disconnection was triggered by proxy that is close to 30seconds before the server timeout, these misclassifed server timeout to 499, especially for EC

Breaking Changes

N/A

Choose a reason for hiding this comment

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

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (1)

server/routerlicious/packages/services-utils/src/morganLoggerMiddleware.ts:136

  • Ensure that the new behavior for classifying server timeouts based on durationInMs > 20000 is covered by tests.
if (res.locals.serverTimeout || durationInMs > 20000) {
@github-actions github-actions bot added area: server Server related issues (routerlicious) base: main PRs targeted against main branch labels Jan 30, 2025
@zhangxin511 zhangxin511 merged commit bfaf365 into main Feb 7, 2025
26 checks passed
@zhangxin511 zhangxin511 deleted the zhangxin/profile499 branch February 7, 2025 14:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: server Server related issues (routerlicious) base: main PRs targeted against main branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants