-
Notifications
You must be signed in to change notification settings - Fork 65.6k
Enhance troubleshooting instructions for Spark deployment #42441
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Added additional troubleshooting steps for deploying Spark.
|
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This pull request enhances the troubleshooting section for Spark deployment from the command line. The author encountered issues where the current latest version of the npm package doesn't work as described in the documentation, requiring a workaround using a runtime.config.json file and the --app parameter.
Changes:
- Expanded the troubleshooting guidance to include a workaround for when updating the Spark SDK doesn't resolve the
--appparameter requirement
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Address review feedback: - Format as numbered list for better readability - Add JSON code block for runtime.config.json content - Specify file location (project root alongside package.json) - Explain that app name is typically the repository name - Add example command showing --app parameter usage
|
1> Added additional troubleshooting steps for deploying Spark.
|
Added additional troubleshooting steps for deploying Spark.
Why:
The instructions did not work for me in any codespaces. I tried many ways to deploy, and the current latest version of the npm is not fully working as described. At some point it may be fine, but for the time being
runtime.config.jsonmust exist and--appmust be used matching it. The npm package isn't open source so I can't fix it. :(What's being changed (if available, include any code snippets, screenshots, or gifs):
Check off the following: