[docs] Document Python callback handle wrapping fix in Aspire 13.6 - #1614
Draft
aspire-repo-bot[bot] wants to merge 1 commit into
Draft
[docs] Document Python callback handle wrapping fix in Aspire 13.6#1614aspire-repo-bot[bot] wants to merge 1 commit into
aspire-repo-bot[bot] wants to merge 1 commit into
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
14 tasks
aspire-repo-bot
Bot
requested a review
from Karol Zadora-Przylecki (karolz-ms)
September 3, 2026 21:31
Contributor
Author
Frontend HTML artifact readyThe latest frontend build uploaded the This comment updates automatically when a new frontend build artifact is uploaded. |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Documents changes from microsoft/aspire#19870
@sebastienrosTargeting
release/13.6based on the source PR milestone13.6(exact match onmicrosoft/aspire.dev).Why
PR #19870 fixed a bug where typed integration callbacks exported as
Action<IResourceBuilder<T>>(for example,configure_containerpassed toWithRedisCommander) received a raw, unwrappedHandlein Python guest code. .NET marshalled the callback argument using the generic builder ATS type ID, while the generated Python wrapper registry looked it up by the concrete resource type ID, so calls likewith_host_portfailed at runtime. Generated callback registrations now carry their concrete handle parameter type IDs, and the Python runtime falls back to that metadata only when no wrapper is registered for the incoming type ID.This is a user-facing fix affecting anyone writing Python AppHosts that use typed resource-builder callbacks, so it needed a documentation update.
What changed
src/frontend/src/content/docs/whats-new/aspire-13-6.mdx— added a bullet under "Integration updates" noting the fix, with the concrete example (configure_container/WithRedisCommander) from the source PR's "User-facing usage" section.src/frontend/src/content/docs/extensibility/multi-language-integration-authoring.mdx— added a note in the "Callback context types and the ATS-first editor pattern" section explaining thatAction<IResourceBuilder<T>>callback parameters are marshalled using the concrete resource type's identity so guest-language wrappers (e.g., Python) resolve to the correct typed handle.Both are edits to existing pages; no new pages were created.