Serve Microsoft Graph selections from precomputed spec slices - #1753
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | aa423aa | Commit Preview URL Branch Preview URL |
Aug 26 2026, 05:59 AM |
Contributor
Cloudflare previewTorn down — the PR is closed. |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-cloud | aa423aa | Aug 26 2026, 06:01 AM |
@executor-js/cli
@executor-js/config
@executor-js/execution
@executor-js/sdk
@executor-js/codemode-core
@executor-js/runtime-quickjs
@executor-js/plugin-file-secrets
@executor-js/plugin-graphql
@executor-js/plugin-keychain
@executor-js/plugin-mcp
@executor-js/plugin-onepassword
@executor-js/plugin-openapi
executor
commit: |
RhysSullivan
marked this pull request as ready for review
August 26, 2026 06:04
This was referenced Aug 26, 2026
Merged
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.
Production traces show the 43MB Graph monolith fetch completing once in the last 30 days — every other preview/add died mid-download with an empty 503 before any parsing began, so #1751's streaming preview cannot help on its own: the isolate can't reliably hold the download alongside its baseline. This removes the monolith from the request path for every covered selection.
slice-build.ts(offline-only) builds one filtered spec per catalog preset plus the default bundle from a whole-parse of the source: the selection's path-items via the samemicrosoftGraphKeepPathItemfilter the runtime applies, components pruned to the transitive$refclosure, emitted as the streamable block-YAML profile so the runtime pipeline treats a slice exactly like a source. Sizes: 4.4–13MB per preset (mail 4.9MB), default bundle 18.3MB, vs 42.9MB upstream; ~3.5k schemas is the closure floor because Graph's schema graph is one connected component.slices.ts(runtime) maps a selection to an asset — single presets exactly, and any combination within the default bundle to the default slice, which the in-bandkeepPathItemfilter then narrows. Full-graph, custom scopes, and out-of-bundle combinations keep the monolith path, as does any slice fetch failure (fallback preserves prior behavior when assets are missing).graph-slicesworkflow regenerates and republishes the assets weekly and on dispatch to thegraph-slicesrelease tag (non-latest data release; initial assets are published).packages/*/*/scripts/**gets the same process-boundary exemptions as the other script directories.Verified: mail selection through the real published slice runs adapter fetch + streaming preview in 162ms at 73MB peak under a 100MB heap (monolith path: 825ms at 129MB — over the isolate budget, matching the prod deaths).
microsoft-graph-defaultandmicrosoft-emulatore2e scenarios pass locally against the live release assets; unit tests cover slice construction, asset resolution, slice-vs-monolith source choice, and fallback.