Bugfix: Fall back when AppearanceElements option is unsupported#168
Merged
Conversation
Some cloud accounts do not support AppearanceElements -> None in CloudDeploy, causing MCP app notebook deployment to fail. Retry without the option when this occurs, and bump paclet to 2.1.1. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Avoid retrying CloudDeploy with AppearanceElements -> None on every invocation once it's known to fail for the current cloud account. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Fixes MCP Apps cloud notebook deployment failures on Wolfram Cloud accounts that don’t support AppearanceElements -> None by retrying CloudDeploy without that option and caching the unsupported status for the rest of the session.
Changes:
- Add
CloudDeploy::appearancenotsupfallback with a session-level cache flag to avoid repeated failed attempts/messages. - Bump paclet version to 2.1.1.
- Document the new fallback behavior in MCP Apps docs.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
Kernel/UIResources.wl |
Implements retry logic around CloudDeploy and adds a session flag to skip unsupported AppearanceElements -> None attempts. |
docs/mcp-apps.md |
Documents the fallback behavior and caching flag. |
PacletInfo.wl |
Bumps paclet version to 2.1.1. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Summary
MCP Appscloud notebook deployment failing on accounts that do not supportAppearanceElements -> Noneby transparently retryingCloudDeploywithout the option onCloudDeploy::appearancenotsup.$includeAppearanceElements) so subsequent deployments skip the failing attempt instead of retrying and emitting a message every time.docs/mcp-apps.md.Fixes #155.
Test plan
AppearanceElements -> None: callWolframLanguageEvaluator/WolframAlphavia an MCP Apps client and confirm the deployed notebook has no footer links.AppearanceElements -> None: call the same tools and confirm deployment succeeds (with footer links visible) rather than failing.$includeAppearanceElementsisTrueand subsequent deployments do not emitCloudDeploy::appearancenotsup.Tests/MCPApps.wltand related MCP Apps tests.🤖 Generated with Claude Code