[large-payload-test] Large Payload Test - 35528516737

Open
#13,543 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
15/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
bash, json
Domain
testing-qa

Research direction

This is an automatically generated PASS report for run 35528516737, not a change request. Start by reviewing the linked Actions run and the reported payload path, then compare the filesystem-read_file result with /workspace/secret.txt. The report already says the secret matched and no issues were detected, so no completion change is specified.

Written by the indexing model from the issue text.

Description

automation mcp-gateway test

Large MCP Payload Access Test Results

Run ID: 35528516737
Status: PASS
Timestamp: 2026-09-20T18:17:43Z

Test Results

  • Expected Secret: test-secret-3d2da7b1-f85d-4f69-b7f9-c810bbaa2b6b
  • Found Secret: test-secret-3d2da7b1-f85d-4f69-b7f9-c810bbaa2b6b
  • Secret Match: YES
  • Payload Path: /tmp/gh-aw/mcp-payloads/3N2ecCDa4Gsb7cYPHOwRf0vYNJoCSs4dLGPZtkArWnUAy7FDJP9MkbzZTt/c01ff9e10bb9ebf551d66f9e7b2a6618/payload.json
  • Payload Size: 820707 bytes

Conclusion

The large payload mechanism worked correctly. filesystem-read_file on the ~500KB /workspace/large-test-file.json returned a truncated response containing payloadPath, payloadPreview, payloadSchema, and originalSize. Reading the full JSON at payloadPath via bash yielded the secret_reference field nested inside content[0].text, which matched the value from /workspace/secret.txt read via filesystem-read_file. No issues detected.

Run URL: https://github.com/github/gh-aw-mcpg/actions/runs/35528516737

Generated by Large Payload Tester · copilot · auto · 21.1 AIC · ⊞ 8.7K · ◷

Dominant language
Go
Stars
176
Forks
51
Avg merge
6h 50m
Merged PRs (30d)
238

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/gh-aw-mcpg

All issues in github/gh-aw-mcpg

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.