You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
AgentEngineSandboxCodeExecutor uses wrong JSON field names for stdout/stderr #3690
This issue has been automatically marked as stale because it has not had recent activity for 7 days after a maintainer requested clarification. It will be closed if no further activity occurs within 7 days.
Apologies for the delayed response. To help us investigate this further, could you please provide more details? Specifically, we would appreciate the full error message, steps to reproduce the issue, and a minimal code example. This will allow us to assist you more effectively.
This issue has been automatically marked as stale because it has not had recent activity for 7 days after a maintainer requested clarification. It will be closed if no further activity occurs within 7 days.
This issue has been automatically marked as stale because it has not had recent activity for 7 days after a maintainer requested clarification. It will be closed if no further activity occurs within 7 days.
Confirming this issue still reproduces on ADK v1.27.2 and through v1.31.1 — affected code paths unchanged from v1.19.0 as described in the original report.
Additional data points from production deployment (April 2026):
Bug 2 (contents vs content): confirmed via live testing. input_files arrive in the sandbox with declared filename but zero bytes; pandas.read_csv raises EmptyDataError, typically surfaced to callers as a vague "file is empty" error rather than a clear field-name mismatch. One-word fix at agent_engine_sandbox_code_executor.py:147 (change 'contents' → 'content') resolves this completely.
Bug 1 (stdout/stderr via msg_out/msg_err): also confirmed. Our patched reader extracts:
Open question on mimeType vs mime_type: in our deployment, sending mimeType (camelCase, matching current ADK behavior) has not produced observable failures — chart files are returned correctly in output_files. Either the Vertex SDK is field-name-normalizing transparently, or this mismatch only matters for specific mime-type-sensitive code paths we haven't exercised. Has anyone hit a concrete failure traceable to the mimeType/mime_type key specifically?
Reference patch:utils/sandbox_executor_patched.py — subclass of AgentEngineSandboxCodeExecutor applying both fixes inline. In continuous production use since April 2026; removes all observed failure modes from this issue.
Would be glad to submit a PR with these fixes (both are narrow, well-tested). Let me know if that's useful.
Activity
adk-bot commentedon Dec 3, 2025
Notification: The author has updated the issue description. Maintainers, please review.
adk-bot commentedon Dec 19, 2025
This issue has been automatically marked as stale because it has not had recent activity for 7 days after a maintainer requested clarification. It will be closed if no further activity occurs within 7 days.
guanerdan commentedon Dec 22, 2025
still waiting....
llalitkumarrr commentedon Jan 7, 2026
Hello @guanerdan ,
Apologies for the delayed response. To help us investigate this further, could you please provide more details? Specifically, we would appreciate the full error message, steps to reproduce the issue, and a minimal code example. This will allow us to assist you more effectively.
adk-bot commentedon Jan 15, 2026
This issue has been automatically marked as stale because it has not had recent activity for 7 days after a maintainer requested clarification. It will be closed if no further activity occurs within 7 days.
adk-bot commentedon Jan 22, 2026
This issue has been automatically marked as stale because it has not had recent activity for 7 days after a maintainer requested clarification. It will be closed if no further activity occurs within 7 days.
5 remaining items
jbets4 commentedon Feb 17, 2026
Attached above is a fix for this issue: #4516
llalitkumarrr commentedon Feb 24, 2026
Thank you @Sudhendra and @jbets4 for your contribution your PR is being reviewed and we appreciate your patience.
Number531 commentedon Apr 24, 2026
Confirming this issue still reproduces on ADK v1.27.2 and through v1.31.1 — affected code paths unchanged from v1.19.0 as described in the original report.
Additional data points from production deployment (April 2026):
Bug 2 (
contentsvscontent): confirmed via live testing.input_filesarrive in the sandbox with declared filename but zero bytes;pandas.read_csvraisesEmptyDataError, typically surfaced to callers as a vague "file is empty" error rather than a clear field-name mismatch. One-word fix atagent_engine_sandbox_code_executor.py:147(change'contents'→'content') resolves this completely.Bug 1 (
stdout/stderrviamsg_out/msg_err): also confirmed. Our patched reader extracts:Open question on
mimeTypevsmime_type: in our deployment, sendingmimeType(camelCase, matching current ADK behavior) has not produced observable failures — chart files are returned correctly inoutput_files. Either the Vertex SDK is field-name-normalizing transparently, or this mismatch only matters for specific mime-type-sensitive code paths we haven't exercised. Has anyone hit a concrete failure traceable to themimeType/mime_typekey specifically?Reference patch: utils/sandbox_executor_patched.py — subclass of
AgentEngineSandboxCodeExecutorapplying both fixes inline. In continuous production use since April 2026; removes all observed failure modes from this issue.Would be glad to submit a PR with these fixes (both are narrow, well-tested). Let me know if that's useful.
mahesh-github commentedon May 28, 2026
Can I check on this issue
fix(code_executors): send correct field names for sandbox input files
fix(code_executors): send correct field names for sandbox input files
fix(code_executors): send correct field names for sandbox input files
fix: send correct field names for sandbox input files
fix: send correct field names for sandbox input files