-
Notifications
You must be signed in to change notification settings - Fork 1
Increase timeout values for Aethel integration test workflow #64
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -27,7 +27,7 @@ async function main() { | |
| }, | ||
| protocol: { | ||
| rateLimitPerMinute: 50, | ||
| messageTimeout: 10000 | ||
| messageTimeout: 120000 | ||
| } | ||
|
Comment on lines
28
to
31
|
||
| }); | ||
| console.log('✓ Framework initialized\n'); | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Increasing the default
messageTimeoutto 120s amplifies a resource issue in_waitForResponse: each REQUEST creates asetTimeoutthat is never cleared when a response arrives, so the timer stays scheduled until it fires (even though it no-ops). Consider storing the timer handle alongside the pending resolve/reject and callingclearTimeoutwhen the response is received (and also on shutdown) to avoid unnecessary queued timers and wakeups under load.