[pull] main from microsoft:main - #1653
Merged
Merged
Conversation
…ixes #333230) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…ession test Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Restore the accidentally-removed teardown/closing of the shift-click
selection test and rewrite the zero-height regression test so it actually
triggers the inverted range: with zero-height dynamic items and a
collapsed viewport, getVisibleRange previously produced { start: 3, end: 0 }
which crashed probeDynamicHeights.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…ment to one line Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Keep the default account available while authentication providers replace a removed session with a new candidate in the same event. Add privacy-safe logs to distinguish interactive and secret-storage replacements. Fixes #333197 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Do not publish an asynchronous refresh result after the current session changes. This keeps a removal-only sign-out final when replacement reconciliation was already in flight. Refs #333197 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Model the Agents web workbench in the account test fixture so browser runs do not skip provider initialization and session-change listener registration. Refs #333197 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…ay-length-333230-aw-33202685801 fix: clamp inverted visible range in ListView to prevent RangeError (fixes #333230)
Model a local editor in Electron and a remote editor in browser tests so the shared default-account replacement behavior is covered outside the Agents window as well. Refs #333197 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* agentHost: normalize secondary assignment context telemetry Promote the SDK wire property as secondary.assignmentcontext and omit the original snake-case field from forwarded workbench events. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * agentHost: avoid copying forwarded telemetry properties Remove the raw SDK assignment context from the newly-created telemetry payload instead of cloning the SDK property bag first. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This reverts commit 5886d26.
…3197-root-cause accounts: preserve sign-in during session replacement
* agentHost: correlate subagent response telemetry Correlate forwarded Copilot SDK response events with logical subagent turns, including the runtime ordering where response telemetry precedes the matching assistant message. Preserve the owning session interaction mode on subagent turn telemetry.\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * agentHost: bound response telemetry correlations Discard late model-call mappings after root or timeout fallback and cover both event orderings with real Copilot session state. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * agentHost: extract model call turn correlation Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * agentHost: avoid uncorrelated response turn IDs Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * agentHost: fix response telemetry test typing Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
agentHost: re-enable GPT tool search The bundled Copilot runtime now includes the parallel tool-call fix, so restore tool search for GPT-5.4, GPT-5.5, and GPT-5.6. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…le-gull Revert "chore: npm audit fix"
* changes Signed-off-by: Dileep Yavanmandha <dileepy@microsoft.com> * Fix Agent Host file link hover labels Format default Markdown link hovers with the host-aware label service while preserving navigation targets and custom titles. Add coverage for WSL paths, Windows host formatting, and existing link behavior. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * changes Signed-off-by: Dileep Yavanmandha <dileepy@microsoft.com> --------- Signed-off-by: Dileep Yavanmandha <dileepy@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…point (#333668) * Reflect startup experiment settings served by the sign-in gated assignments endpoint * update comment * Feedback updates
Exclude tests from CodeQL analysis Reduce the CodeQL database size so default-branch overlay databases can be cached and reused by pull request scans. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Fix skill completions in automations Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 24f4e305-8042-4e9f-8061-72525532fc1b * Fix Automation suggestion popup placement Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 24f4e305-8042-4e9f-8061-72525532fc1b * Preserve runtime skill completions Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 24f4e305-8042-4e9f-8061-72525532fc1b --------- Copilot-Session: 24f4e305-8042-4e9f-8061-72525532fc1b
* input pickers responsiveness v2 * address comments
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3f172890-b580-41e9-a79d-c7af8ee372c2
* managed settings: reuse cached policy on reload instead of refetching When forceRemoteSettingsRefresh is not effective, a fresh cached managed-settings response now satisfies startup without a network round-trip, matching the sibling entitlements/token/MCP fetches which only refetch once the cache goes stale. Previously a per-process gate (hasFetchedThisProcess) forced one /managed_settings request on every reload even with a fresh cache and no policy requirement, which for a user without an enterprise policy fanned out into one 404 per GitHub session. Cache reuse is scoped: a cached response is only reused when it was captured for the current account, authentication provider, and endpoint (a legacy cache with no recorded scope is trusted), so a previous GitHub Enterprise host's policy is not applied after switching scopes. An outstanding client_update_required compatibility error is never served from cache: it is revalidated on the next refresh so the fail-closed block clears once the client or server recovers, instead of lingering for the full cache lifetime. The fail-closed path is otherwise unchanged: when the control is effective, only a fresh successful response for the current account, provider, and endpoint clears the requirement. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Trigger signed commit verification Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * managed settings: scope failure fallbacks Do not retain or relabel managed settings cached for a different account provider or endpoint when refresh fails or automatic retries are blocked. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.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.
12 participants
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 : )