Skip to content

Post-2026.1.0.52 sweep, Tier 3: diagram layout key, Linux ES resilience, SAML XXE, bug fixes - #26

Closed
nahumtimerman wants to merge 3 commits into
docs/2026.1-patch-sweep-tier2from
docs/2026.1-patch-sweep-tier3
Closed

Post-2026.1.0.52 sweep, Tier 3: diagram layout key, Linux ES resilience, SAML XXE, bug fixes#26
nahumtimerman wants to merge 3 commits into
docs/2026.1-patch-sweep-tier2from
docs/2026.1-patch-sweep-tier3

Conversation

@nahumtimerman

Copy link
Copy Markdown
Collaborator

Final batch of the post-2026.1.0.52 catch-up. Based on docs/2026.1-patch-sweep-tier2 (#25), which is based on #24 — all three edit whats-new.md. Merge #24#25 → this.

Preserve diagram arrangement on View Style change

CS 189995 / 189996 / 190004 (ticket 67465, WI 19310). New PreserveDiagramLayoutOnViewStyleChange Portal key, default False. Documented in the customer keys repository because it is declared AppSettingVisibility.Customer — including the caveat from the setting's own description that enabling it can make Large cards overlap on a diagram arranged in a smaller View Style. The three coordinate fixes that landed unconditionally (Arrange, drag-to-move, sticky-note resize) are called out separately since they apply regardless of the key.

Linux Execution Server resilience

CS 189890 / 189891 (ticket 67293). Described by behavior, not by key: MinThreadPoolWorkerThreads (200), BeginExecutionMaxRetryCount (10) and BeginExecutionRetryIntervalSec (6) all take the AppSetting default visibility, which is AppSettingVisibility.Support — so they don't belong in the customer configuration keys repository. What's documented is what a user can observe: the agent wedging under driver-spawn bursts, the ~100s dispatch tolerance replacing a few seconds, and the Linux venv bin-vs-Scripts path fix.

Security

CS 189894 — unauthenticated XXE (CWE-611) on the Portal SAML ACS endpoint, added to the 2026.1 Security Updates with an explicit note for SSO/SAML deployments.

Bug fixes

Four bullets: diagram duplicate resource alias (CS 189961, has a release note), Blueprint not found loop on domain switch (CS 189991), HTTP 500 downloading a shell/provisioning script with an extensionless stored file name (CS 189989), Properties dialog end time for a non-admin on a sandbox extended past its cap (CS 190005).

Deliberately not documented

  • Docker ES get-pip curl→wget (CS 189983/189984/189986) — image build plumbing; the failing builds never shipped.
  • ExportBlueprintPackage/ImportBlueprintPackage (CS 189912/189917/189921) — CS 189940 replaced them with the ExportBlueprint/ImportBlueprint pair already documented in Document the new ExportBlueprint/ImportBlueprint APIs (2026.1) #22, so documenting them would describe an API that was superseded before release.
  • Dotfuscator, TCL/XmlToHtml generation, nightly-red fixes, CI/csproj changesets.

npx docusaurus build passes; the 3 broken links reported are pre-existing and unrelated.

🤖 Generated with Claude Code

nahumtimerman and others added 2 commits September 9, 2026 17:28
…inputs, category validation

Documents the three behavior-changing items that landed on 2026.1 after the
2026.1.0.52 pass (#18) and were not covered by #19-#22.

Python 3 upgraded to 3.13.15 x64 (Trunk CS 189988/189997/189999, backported
in CS 190003). This is the WINDOWS bundled slot only - the Docker ES image
still builds Python 3.9.9, and so do the Linux VA and the from-script ES, so
every page states the platform split rather than a blanket "CloudShell now
uses 3.13". Python 2.7.18 is untouched. Also corrects setting-up-dev-env.md,
which #23 had just updated to say the bundled version is 3.9.9 - true when
it merged on Sep 6, wrong when the upgrade landed on Sep 8.

Global inputs kept on save as blueprint, with the new
KeepResourceGlobalInputsOnSaveAsBlueprint key (CS 189903/189905/189914).
Default is true, which is a behavior change on upgrade: inputs that fronted a
resource requirement used to be dropped and are now visible in the Reserve
dialog and the blueprint editor. Documented as a customer-visible key on the
Server (AppSettingVisibility.Customer, read by ServiceConfigSettingsLoader).

Blueprint import now fails on a category missing from the target domain
instead of silently dropping the association (CS 189942). The
ExportBlueprint/ImportBlueprint page from #22 already stated this, so it
needed no correction - only the release notes did.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
… by display name

Driver command queue inspection and recovery (Trunk CS 189900, ticket 67008).
New how-to page for the four sysadmin-gated methods - GetRunningCommands,
GetResourceCommandExecutions, CancelResourceCommand, ClearResourceCommands -
plus a What's New entry.

Signatures, parameter semantics and the sysadmin requirement come from
Tools/API/XmlDocumentation/TestShell API/ApiDocumentation.xml, where all four
are registered Lang="all". The response shape is RunningCommandListInfo from
ApiCommandResult.cs: a Commands list of RunningCommandInfo with ExecutionId,
ResourceFullName, CommandName, Status, StartTime and ReservationId. The page
leads with why the resource-scoped pair exists - a command belonging to a
previous, possibly ended, sandbox blocking an exclusive non-concurrent
resource, which a new sandbox cannot see because its view is reservation
scoped - and notes that ClearResourceCommands cancels out-of-band so it does
not wait behind the command it is clearing, which is what makes it usable
from Setup.

Sandbox owners and permitted users accepted by display name (CS 189998 +
190000, ticket 67309; release note Docs/ReleaseNotes/2026.1/
sandbox-owner-resolved-by-display-name.md). Keeps the two points that make it
safe to rely on: usernames are matched first so nothing existing changes, and
an ambiguous display name is rejected rather than resolved arbitrarily.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@nahumtimerman
nahumtimerman force-pushed the docs/2026.1-patch-sweep-tier2 branch from d0a900f to 6eb770b Compare September 9, 2026 14:40
…silience, SAML XXE, bug fixes

Closes out the catch-up for everything that landed on 2026.1 after
2026.1.0.52.

PreserveDiagramLayoutOnViewStyleChange (CS 189995/189996/190004, ticket 67465
/ WI 19310). Documented as a customer key on the Portal - it is declared
AppSettingVisibility.Customer, unlike the ES/Server keys below - with the
overlap caveat from the setting's own description. The three unconditional
coordinate fixes (Arrange, drag-to-move, sticky-note resize) are noted
separately, since they apply whether or not the key is set.

Linux/Mono ES resilience (CS 189890/189891, ticket 67293). Described by
behavior rather than by key: MinThreadPoolWorkerThreads (200),
BeginExecutionMaxRetryCount (10) and BeginExecutionRetryIntervalSec (6) all
default to AppSettingVisibility.Support, so they do not belong in the customer
configuration keys repository. The user-visible facts are the wedged agent
under driver-spawn bursts, the ~100s dispatch tolerance, and the Linux venv
bin-vs-Scripts path fix.

SAML ACS XXE (CS 189894, CWE-611) added to Security Updates - unauthenticated
endpoint, so it is called out for SSO/SAML deployments.

Bug fixes: diagram duplicate resource alias (CS 189961, release note),
'Blueprint not found' loop on domain switch (CS 189991), 500 downloading a
shell or provisioning script with an extensionless stored file name
(CS 189989), Properties dialog end time for a non-admin on an extended
sandbox (CS 190005).

Deliberately not documented: the Docker ES get-pip curl/wget change
(CS 189983/189984/189986) is image build plumbing that never reached a
released image, plus Dotfuscator, TCL/XmlToHtml generation, nightly-red and
CI-only changesets. ExportBlueprintPackage/ImportBlueprintPackage
(CS 189912/189917/189921) are also omitted: CS 189940 replaced them with the
ExportBlueprint/ImportBlueprint pair already documented in #22.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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