[pull] main from microsoft:main - #1665
Merged
Merged
Conversation
* agentHost: scale E2E protocol timeouts for CI contention The four Agent Host E2E entrypoints run in parallel on one CI agent. On a slow run every failure was a short wait expiring rather than a wrong result: cleanup `subscribe` on a never-restored session after a host restart, `createChat`, the create-pr operation poll, and a review-changed notification all hit the 5s default that only ever scaled for Windows and coverage mode. - Default protocol operation timeout is 20s on CI (local stays 5s/8s). - Harness release() uses the extended cleanup bound for its subscribe calls, matching the dispose calls, so a slow cleanup no longer fails a passing test and forces a server restart. - changesetSuite operation polling allows 300 retries on CI, and its peer chat createChat passes 30s like the other suites. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * agentHost: tighten E2E cleanup bounds and comments Address review: keep the cleanup subscribe bound at 30s on CI rather than the 90s dispose bound so worst-case teardown stays closer to the hook budget, and shorten the explanatory comments. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
* agentHost: classify inline chat telemetry Use the existing ephemeral-session marker to identify Agent Host turns that started from inline chat. - Add inline to the bounded message origin telemetry values. - Apply the value to direct, queued, resumed, and subagent turns. - Include message origin in completion, failure, hang, and recovery events. - Add coverage for standard, queued, failed, and hung turns. (Commit message generated by Copilot) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * agentHost: clarify inline telemetry origin Explain that message origin telemetry includes host-owned classifications and that inline is derived from the existing ephemeral-session marker. (Commit message generated by Copilot) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* browser: skip unused screenshot after load failure Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * browser: centralize placeholder screenshot guard Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * browser: restart screenshot capture after navigation Restart the renderer screenshot loop when URL or error state changes without requiring a visibility transition. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Kyle Cutler <kycutler@microsoft.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )