Skip to content

Increase timeout values for Aethel integration test workflow#64

Merged
colleenpridemore merged 2 commits into
mainfrom
copilot/fix-aethel-integration-timeouts
Jan 24, 2026
Merged

Increase timeout values for Aethel integration test workflow#64
colleenpridemore merged 2 commits into
mainfrom
copilot/fix-aethel-integration-timeouts

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Jan 15, 2026

The Aethel integration test workflow fails due to timeouts in both job execution (5 min limit) and inter-agent communication (30s default). Error logs show "Request timeout" during step 6 and job-level timeout after 5 minutes.

Changes

  • Workflow timeout: 5 → 10 minutes for job execution
  • API timeout: 60s → 120s for ASI:One API calls (ASI_ONE_TIMEOUT env var)
  • Protocol defaults: 30s → 120s default messageTimeout in CommunicationProtocol.js
  • Example config: 10s → 120s messageTimeout in aethel-integration.js

All timeout values unified at 120s (2 min) to provide consistent headroom for inter-agent communication and AI API calls.

Original prompt

Problem

The Aethel integration test workflow is failing due to timeouts in two areas:

  1. Job timeout: The "Run Aethel integration example" step times out after 5 minutes
  2. Inter-agent communication timeout: The communication protocol's messageTimeout is set to 30 seconds (default), causing "Request timeout" errors during inter-agent communication in step 6 of the example

Error logs from Job 60402269110:

✗ Inter-agent communication failed: Request timeout
##[error]The action 'Run Aethel integration example' has timed out after 5 minutes.

Solution Required

Make the following changes to fix the timeout issues:

1. Update .github/workflows/aethel-integration-test.yml

File: .github/workflows/aethel-integration-test.yml
CommitOID: 9af12fe
BlobSha: db59352221e94949530e0e13575bc97d2b2fc527

Change line 42 from:

echo "ASI_ONE_TIMEOUT=60000" >> .env

to:

echo "ASI_ONE_TIMEOUT=120000" >> .env

Change line 56 from:

timeout-minutes: 5

to:

timeout-minutes: 10

2. Update agents/examples/aethel-integration.js

File: agents/examples/aethel-integration.js
CommitOID: 9af12fe
BlobSha: fdc6966453b682a46b25774fe247a375502903e2

Change line 30 from:

messageTimeout: 10000

to:

messageTimeout: 120000

3. Update agents/communication/CommunicationProtocol.js

File: agents/communication/CommunicationProtocol.js
CommitOID: 9af12fe
BlobSha: 3b92cb832279c802a2b2b9d0e408b748e65ad453

Change line 76 from:

messageTimeout: config.messageTimeout || 30000, // 30 seconds

to:

messageTimeout: config.messageTimeout || 120000, // 120 seconds (2 minutes)

Expected Outcome

After these changes:

  • The workflow will have 10 minutes to complete instead of 5
  • The ASI:One API timeout will be 120 seconds instead of 60 seconds
  • Inter-agent communication will have 120 seconds to complete instead of 30 seconds
  • The integration test should pass without timeout errors

Testing

Once the PR is merged, the workflow will automatically run on the next push to main or when a PR is created. The inter-agent communication step should complete successfully within the new timeout limits.

This pull request was created from Copilot chat.


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Co-authored-by: colleenpridemore <4281084+colleenpridemore@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix Aethel integration test timeout issues Increase timeout values for Aethel integration test workflow Jan 15, 2026
Copy link
Copy Markdown
Contributor

@colleenpridemore colleenpridemore left a comment

Choose a reason for hiding this comment

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

Ok!

@colleenpridemore colleenpridemore marked this pull request as ready for review January 24, 2026 02:14
Copilot AI review requested due to automatic review settings January 24, 2026 02:14
@colleenpridemore colleenpridemore merged commit 0d74224 into main Jan 24, 2026
3 checks passed
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Adjusts timeouts across the Aethel integration test workflow and agent communication defaults to reduce CI failures caused by request and job timeouts.

Changes:

  • Increased GitHub Actions step timeout for the Aethel integration example (5 → 10 minutes).
  • Increased default inter-agent messageTimeout in CommunicationProtocol (30s → 120s).
  • Updated the Aethel integration example’s protocol messageTimeout (10s → 120s).

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File Description
.github/workflows/aethel-integration-test.yml Extends CI execution window and writes a longer ASI:One timeout into .env.
agents/examples/aethel-integration.js Updates protocol configuration to allow longer inter-agent message waits.
agents/communication/CommunicationProtocol.js Raises the protocol-wide default message timeout to reduce “Request timeout” failures.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines 28 to 31
protocol: {
rateLimitPerMinute: 50,
messageTimeout: 10000
messageTimeout: 120000
}
Copy link

Copilot AI Jan 24, 2026

Choose a reason for hiding this comment

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

The workflow writes ASI_ONE_TIMEOUT into .env, but this example never passes aethelConfig.timeout into new AethelAgent(...), so API requests will still use AethelAgent’s internal default (30s). To make the increased API timeout effective, wire the value through (e.g., include timeout: aethelConfig.timeout in the agent constructor config) or remove the .env timeout if it’s intentionally unused.

Copilot uses AI. Check for mistakes.
Comment on lines 75 to 79
maxQueueSize: config.maxQueueSize || 100,
messageTimeout: config.messageTimeout || 30000, // 30 seconds
messageTimeout: config.messageTimeout || 120000, // 120 seconds (2 minutes)
rateLimitPerMinute: config.rateLimitPerMinute || 100,
enableEncryption: config.enableEncryption || false,
...config
Copy link

Copilot AI Jan 24, 2026

Choose a reason for hiding this comment

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

Increasing the default messageTimeout to 120s amplifies a resource issue in _waitForResponse: each REQUEST creates a setTimeout that 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 calling clearTimeout when the response is received (and also on shutdown) to avoid unnecessary queued timers and wakeups under load.

Copilot uses AI. Check for mistakes.
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.

3 participants