fix: increase server timeout from 5s to 30s#184
Merged
jakebromberg merged 2 commits intomainfrom Feb 27, 2026
Merged
Conversation
dba3252 to
b7a30ef
Compare
The 5-second timeout was too aggressive for endpoints that make multiple database queries or external API calls. Co-authored-by: Cursor <cursoragent@cursor.com>
Use narrowing guard instead of non-null assertion to satisfy @typescript-eslint/no-unnecessary-type-assertion.
f084bef to
a884010
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
server.setTimeout(5000)inapps/backend/app.tsset a 5-second timeout on all HTTP sockets, which was too aggressive for endpoints making multiple DB queries or external API calls.server.setTimeout(30000)).app.tsand asserts the timeout value is at least 30,000ms.Test plan
tests/unit/config/server-timeout.test.tsfails with the old 5s valueCloses #23
Made with Cursor