Forum Discussion
Debug Spark Job Definition - No Response when selecting debug and Exceeded the amount of requests
- 1 year ago
Hi Anonymous ,
I can confirm Microsoft have fixed the bug in the pre-release Synapse VS Code extension for Visual Studio Code. I've just finished testing this morning, hence the delayed response.
Hi DanielAmbler,
Thanks for reaching out to the Microsoft fabric community forum.
The first issue involves exceeding request limits, which can often be resolved by waiting or adjusting usage patterns.
Below troubleshooting steps can resolve your issue:
- Avoid refreshing your workspace frequently. The changes will appear in due course without the need for constant refreshes.
- A simple restart can clear temporary request queues. Other extensions might be making requests in the background, contributing to the limit. Temporarily disable some extensions to identify the issue.
The second issue involves the debugging feature not working, which may require checking configurations, trust settings, and extension updates.
Following these steps should assist in resolving these problems:
- Ensure you have a correctly configured launch.json file within your .vscode folder (create it if it's missing). This file specifies how VS Code should debug your Spark application. It should include information about the Spark application's entry point and any necessary parameters.
Refer to below documentation for proper launch.json configuration for Spark:
- Review the VS Code output panel (usually accessed through View > Output) for any error messages related to the Synapse extension or your Spark job debugging attempt.
- The extension could have a bug. Try updating it or reinstalling it. Sometimes, a simple restart can resolve minor software glitches.
For detail information kindly refer the below documentation:
I hope my suggestions give you good ideas, if you need any further assistance, feel free to reach out.
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
- Anonymous1 year agoNot applicable
Hi DanielAmbler,
We haven't received any updates from you in a while and wanted to follow up to see if you had a chance to review the provided information. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you. - DanielAmbler1 year agoHelper II
Hi Anonymous ,
I can confirm Microsoft have fixed the bug in the pre-release Synapse VS Code extension for Visual Studio Code. I've just finished testing this morning, hence the delayed response.