-
Notifications
You must be signed in to change notification settings - Fork 183
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
Debug session process exited with status: exited abnormally with code 1 #665
Comments
check stderrr buffer and I hope that this is not the whole json file, because it is not valid json. |
Thanks for the reply and apologies for not posting the complete json file before.
The output from the stderr buffer,
|
I am using doom emacs and i have this in my
|
That adapter is broken, we have to fix it. I think that there was a bug about that. |
Understood, thanks having a look. For now, ive manually extracted the debug program. |
I'm seeing the same error when I run
On further inspection, I found the "zip" is not a zip at all, but JSON indicating (at face value) some kind of rate limit failure:
pretty printed: {
"eventId": 3000,
"errorCode": 0,
"typeKey": "RequestBlockedException",
"typeName": "Microsoft.TeamFoundation.Framework.Server.RequestBlockedException, Microsoft.TeamFoundation.Framework.Server",
"message": "Request was blocked due to exceeding usage of resource 'Count' in namespace 'AnonymousId'. For more information on why your request was blocked, see the topic \"Rate limits\" on the Microsoft Web site (https://go.microsoft.com/fwlink/?LinkId=823950).",
"innerException": null,
"$id": "1"
} |
Well it seems we are not the only one with this issue, please refer to this issue message for a workaround. It worked for me. |
Thanks for linking @texaco. @sparkcanon @yyoncho I suggest this be closed as a dupe |
When I run
dap-debug
and select a configuration template, I seeDebug session process exited with status: exited abnormally with code 1
as an echo message.The configuration I am running:
The text was updated successfully, but these errors were encountered: