-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
Funky event order (active before start) #31589
Comments
|
@weinand This is what I am seeing now. The order seems correct, but the
|
@jrieken I can not repro this. 'use strict';
// The module 'vscode' contains the VS Code extensibility API
// Import the module and reference it with the alias vscode in your code below
import * as vscode from 'vscode';
// this method is called when your extension is activated
// your extension is activated the very first time the command is executed
export function activate(context: vscode.ExtensionContext) {
// Use the console to output diagnostic information (console.log) and errors (console.error)
// This line of code will only be executed once when your extension is activated
console.log('Congratulations, your extension "tsext-first" is now active!');
// The command has been defined in the package.json file
// Now provide the implementation of the command with registerCommand
// The commandId parameter must match the command field in package.json
vscode.debug.onDidStartDebugSession(e => {
console.log('START', e.id);
})
vscode.debug.onDidTerminateDebugSession(e => {
console.log('STOP', e.id);
})
vscode.debug.onDidChangeActiveDebugSession(e => {
console.log('CHANGE ACTIVE', e.id);
})
vscode.debug.onDidReceiveDebugSessionCustomEvent(e => {
console.log('CUSTOM EVENT', e.session.id, e.event);
})
let disposable = vscode.commands.registerCommand('extension.sayHello', () => {
// The code you place here will be executed every time your command is executed
const configuration = vscode.workspace.getConfiguration('testExtension', vscode.window.activeTextEditor.document.uri);
configuration.get('resourceConfiguration');
console.log(configuration.inspect('resourceConfiguration'));
console.log(configuration.inspect('resourceConfiguration'));
// Display a message box to the user
vscode.window.showInformationMessage('Hello World!');
});
context.subscriptions.push(disposable);
}
// this method is called when your extension is deactivated
export function deactivate() {
} Here's a js program that I am debugging function fib(i) {
if (i < 2) {
for(var t = 0; t < 10; t++) {
console.log(t);
}
return 1;
}
return fib(i - 1) + fib(i - 2);
}
console.log(fib(20)); |
This issue has been closed automatically because it needs more information and has not had recent activity. Please refer to our guidelines for filing issues. Thank you for your contributions. |
Should this have been closed? |
This issue has been closed automatically because it needs more information and has not had recent activity. Please refer to our guidelines for filing issues. Thank you for your contributions. |
testing #31475
Have an extension with listener as shown below. Debug a node.js app that just interval's forever and notice the following order of events. Weird is that
CUSTOM EVENT
comes first (tho not always) and thatCHANGE ACTIVE
comes beforeSTART
The text was updated successfully, but these errors were encountered: