Skip to content

fix: avoid host-only eval crash when app_agent_log is empty#306

Open
grtninja wants to merge 1 commit intomicrosoft:pre-releasefrom
grtninja:codex/fix-304-host-only-eval
Open

fix: avoid host-only eval crash when app_agent_log is empty#306
grtninja wants to merge 1 commit intomicrosoft:pre-releasefrom
grtninja:codex/fix-304-host-only-eval

Conversation

@grtninja
Copy link
Copy Markdown

Summary

  • guard host-only evaluation paths so app_agent_log=[] no longer crashes user_content_construction_head_tail()
  • keep the existing initial-screenshot behavior when an AppAgent step is present
  • add focused regression coverage for empty and non-empty AppAgent logs

Why

Fixes #304. Host-only tasks can complete without any AppAgent steps, so indexing trajectory.app_agent_log[0] is unsafe and can terminate evaluation with IndexError.

Validation

  • python -m pytest -q tests\\unit\\test_eva_prompter_host_only.py

Risk Notes

  • small evaluation-path change only
  • no automation-flow refactor
  • no policy or security-surface change

@grtninja
Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree

I've been a Windows Insider since January 30, 2015, and a long-time Windows feedback participant.

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.

1 participant