code-server-2/packages/protocol/src/proto/node.proto

syntax = "proto3";

message NewEvalMessage {
	uint64 id = 1;
	string function = 2;
	repeated string args = 3;
	// Timeout in ms
	uint32 timeout = 4;
	// Create active eval message.
	// Allows for dynamic communication for an eval
	bool active = 5;
}

message EvalEventMessage {
	uint64 id = 1;
	string event = 2;
	repeated string args = 3;
}

message EvalFailedMessage {
	uint64 id = 1;
	string response = 2;
}

message EvalDoneMessage {
	uint64 id = 1;
	string response = 2;
}

message Ping {}

message Pong {}
Add evaluate 2019-01-11 19:33:44 +00:00			`syntax = "proto3";`

			`message NewEvalMessage {`
Add commands (#2) * Add remote command execution * Add tests for environment variables and resize * Fix tab spacing, add newlines * Remove extra newline * Add fork 2019-01-12 19:44:29 +00:00			`uint64 id = 1;`
			`string function = 2;`
			`repeated string args = 3;`
			`// Timeout in ms`
			`uint32 timeout = 4;`
Add active evals (#25) * Add active evals * Convert type of stats to date or string * Fix generic overloads for run * Lower evaluate timeout * Add comment for createWriteStream 2019-01-30 00:48:02 +00:00			`// Create active eval message.`
			`// Allows for dynamic communication for an eval`
			`bool active = 5;`
			`}`

			`message EvalEventMessage {`
			`uint64 id = 1;`
			`string event = 2;`
			`repeated string args = 3;`
Add evaluate 2019-01-11 19:33:44 +00:00			`}`

			`message EvalFailedMessage {`
Add commands (#2) * Add remote command execution * Add tests for environment variables and resize * Fix tab spacing, add newlines * Remove extra newline * Add fork 2019-01-12 19:44:29 +00:00			`uint64 id = 1;`
Include code in stringified errors This is done by returning the entire error stringified instead of just the message. This fixes the issue with the "save as" dialog. 2019-02-26 21:46:05 +00:00			`string response = 2;`
Add evaluate 2019-01-11 19:33:44 +00:00			`}`

			`message EvalDoneMessage {`
Add commands (#2) * Add remote command execution * Add tests for environment variables and resize * Fix tab spacing, add newlines * Remove extra newline * Add fork 2019-01-12 19:44:29 +00:00			`uint64 id = 1;`
Make everything use active evals (#30) * Add trace log level * Use active eval to implement spdlog * Split server/client active eval interfaces Since all properties are not valid on both sides * +200% fire resistance * Implement exec using active evaluations * Fully implement child process streams * Watch impl, move child_process back to explicitly adding events Automatically forwarding all events might be the right move, but wanna think/discuss it a bit more because it didn't come out very cleanly. * Would you like some args with that callback? * Implement the rest of child_process using active evals * Rampant memory leaks Emit "kill" to active evaluations when client disconnects in order to kill processes. Most likely won't be the final solution. * Resolve some minor issues with output panel * Implement node-pty with active evals * Provide clearTimeout to vm sandbox * Implement socket with active evals * Extract some callback logic Also remove some eval interfaces, need to re-think those. * Implement net.Server and remainder of net.Socket using active evals * Implement dispose for active evaluations * Use trace for express requests * Handle sending buffers through evaluation events * Make event logging a bit more clear * Fix some errors due to us not actually instantiating until connect/listen * is this a commit message? * We can just create the evaluator in the ctor Not sure what I was thinking. * memory leak for you, memory leak for everyone * it's a ternary now * Don't dispose automatically on close or error The code may or may not be disposable at that point. * Handle parsing buffers on the client side as well * Remove unused protobuf * Remove TypedValue * Remove unused forkProvider and test * Improve dispose pattern for active evals * Socket calls close after error; no need to bind both * Improve comment * Comment is no longer wishy washy due to explicit boolean * Simplify check for sendHandle and options * Replace _require with __non_webpack_require__ Webpack will then replace this with `require` which we then provide to the vm sandbox. * Provide path.parse * Prevent original-fs from loading * Start with a pid of -1 vscode immediately checks the PID to see if the debug process launch correctly, but of course we don't get the pid synchronously. * Pass arguments to bootstrap-fork * Fully implement streams Was causing errors because internally the stream would set this.writing to true and it would never become false, so subsequent messages would never send. * Fix serializing errors and streams emitting errors multiple times * Was emitting close to data * Fix missing path for spawned processes * Move evaluation onDispose call Now it's accurate and runs when the active evaluation has actually disposed. * Fix promisifying fs.exists * Fix some active eval callback issues * Patch existsSync in debug adapter 2019-02-19 16:17:03 +00:00			`string response = 2;`
Add evaluate 2019-01-11 19:33:44 +00:00			`}`
Add ping/pong to the protocol (#2) 2019-03-05 03:26:17 +00:00
			`message Ping {}`

			`message Pong {}`