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

Open
  • Is something wrong?
#16,483 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Under an hour
Newbie friendliness
5/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Domain
testing

Research direction

This is an automated run record from the Large Payload Tester workflow, and it asks for no code change. The payload path and secret match are reported as a PASS, with filesystem-read_file on /workspace/large-test-file.json as the trigger. There is no defined "done" for a newcomer, so a maintainer should close it or confirm it needs no action.

Written by the indexing model from the issue text.

Description

automation mcp-gateway test

Large MCP Payload Access Test Results

Run ID: 43523624006
Status: PASS
Timestamp: 2026-11-13T23:01:30Z

Test Results

  • Expected Secret: test-secret-f6f64445-8180-4828-9abc-b0632459635b
  • Found Secret: test-secret-f6f64445-8180-4828-9abc-b0632459635b
  • Secret Match: YES
  • Payload Path: /tmp/gh-aw/mcp-payloads/REDACTED/d2e9a0a206dd18387ad427e6eac852ec/payload.json
  • Payload Size: 820707 bytes

Conclusion

filesystem-read_file on /workspace/large-test-file.json triggered the large payload mechanism and returned a payloadPath. The payload file was readable via bash. Note: the payload JSON is an MCP result wrapper (content[0].text), and secret_reference is in the JSON string inside that text field, not at the top level of the payload file. It matched the secret from /workspace/secret.txt.

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

Generated by Large Payload Tester · copilot · routed: sonnet55 high · ~20 AIC · ⊞ 2.1K · ◷

Dominant language
Go
Stars
188
Forks
60
Avg merge
6h 45m
Merged PRs (30d)
198

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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.